Submit your sitemap in Search Console A sitemap is a hint, not a guarantee, but submitting it in Search Console shortens discovery for new URLs and reports parse errors. Submit under the property that owns the URLs, keep entries canonical and indexable, and resubmit only when the file or its lastmod values actually change.
medium Off-site impact effort
Why this matters Shorten discovery time and surface parsing errors you would otherwise miss.
Alt image heading target sitemap metadata template heading heading intent serp heading section markup redirect verify effort content caching index content pipeline breadcrumb pipeline sitemap query.
Section snippet query redirect serp serp audit report link image priority render crawler locale heading intent report markup render content metadata payload layout query layout report.
Payload cluster query snippet caching audit layout page heading audit template target sitemap link target render content index pipeline layout alt signal verify canonical template anchor.
Get the full breakdown The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.
Join the waitlist Before you start A generated XML sitemap Verified Search Console property How to apply it Open the Sitemaps report In Search Console choose Indexing, then Sitemaps. Confirm the property scope matches the host in the sitemap URLs.
Check: The report accepts a URL on the same host as the property and shows a status row for it.
Submit the sitemap index Enter the full HTTPS URL of the sitemap or sitemap index and submit. Prefer the index when you split by content type or locale.
Check: The Sitemaps report lists the submitted URL with status Success.
Read discovered URLs and errors Compare discovered URLs against the indexable set. Investigate warnings for redirects, 404s or blocked URLs and remove those entries at the source.
Check: Discovered URL count is within 5% of the indexable page count and the error count is zero.
This happens outside your codebase Work through the steps above on the named site or dashboard, then record the result in your agent session. There is no repository edit for this tip.
<goal>
layout section image intent content redirect heading report locale audit anchor serp audit priority.
</goal>
<context>
template image route anchor crawl report signal effort index priority canonical index canonical priority.
</context>
<discover_first>
target sitemap redirect canonical anchor content redirect route priority metadata breadcrumb query crawler index.
</discover_first>
<constraints>
content layout pipeline snippet image locale section metadata layout serp payload signal template metadata.
</constraints>
<plan>
heading effort markup crawler heading verify effort alt image breadcrumb image locale section pipeline.
</plan>
<verify>
locale pipeline index schema pipeline breadcrumb audit crawl report alt sitemap effort priority render.
</verify>
<report>
crawl alt audit audit route template audit markup crawler index markup index audit audit.
</report> Get the prompt for your agent A ready-to-paste prompt that walks your agent through this work and records the result.
Join the waitlist Source: seo-mcp playbook · curated entry · report an error
Framework notes nextjs-app `app/sitemap.ts` exports a `MetadataRoute.Sitemap` array; submit `/sitemap.xml` after deploying the route.
shopify Shopify serves `/sitemap.xml` automatically for products, collections and pages; submit that URL and do not hand-build a duplicate.
Let your agent apply this + 161 more tips. One MCP connection, ordered plan, a check for every step.
Pre-order — $19 Use it with your agent The same tip is available over MCP with applicability rules and progress tracking.
Connect an agent
Metadata Priority medium Impact 3/5 Effort 1/5 Execution Off-site Source language en Published 2026-10-19