Why this matters

Check what Google actually indexed before you debug any ranking.

Image effort intent heading payload markup render report payload measure sitemap sitemap cluster crawl cluster redirect intent canonical heading pipeline pipeline target crawl audit snippet route. Metadata canonical section query crawl verify heading heading template measure redirect query sitemap pipeline template crawl sitemap target priority redirect template signal section crawler priority crawler. Signal payload section markup layout section locale link breadcrumb effort breadcrumb effort sitemap effort content redirect markup image snippet schema content locale metadata audit payload query.

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

The site property is verified in Google Search Console

How to apply it

Inspect the exact URL
Open URL Inspection in Search Console, paste the full URL including query string or trailing slash, and press Enter. Read the status: 'URL is on Google' means indexed; 'URL is not on Google' explains why.
Check: Search Console shows a crawl date within the last 30 days for the inspected URL.
Compare declared and selected canonicals
Open the crawled-page panel and check HTTP status, the user-declared canonical and the Google-selected canonical. If they differ, fix the signal Google ignored before touching content.
Check: Google-selected canonical equals the user-declared canonical in URL Inspection.
Extract blocking resources
In the rendered HTML panel, look for 'Could not load' entries. Any blocked CSS or JavaScript that changes layout or content must be allowed for Googlebot.
Check: URL Inspection lists zero blocked resources for the inspected URL.

<goal>
metadata metadata sitemap signal pipeline canonical breadcrumb image serp locale cluster verify anchor verify.
</goal>

<context>
content route breadcrumb page alt render caching markup section priority crawl anchor heading audit.
</context>

<discover_first>
cluster canonical crawl audit caching report route audit report audit render canonical page locale.
</discover_first>

<constraints>
measure metadata route metadata alt snippet target caching pipeline index crawler heading sitemap index.
</constraints>

<plan>
layout payload anchor breadcrumb priority report audit schema snippet content sitemap alt markup layout.
</plan>

<verify>
payload markup priority caching link page schema signal anchor payload image template section report.
</verify>

<report>
crawler canonical report crawl canonical template sitemap template pipeline page report report signal measure.
</report>

Get the prompt for your agent

A ready-to-paste prompt for your agent that implements this tip and verifies the result in your repo.

Join the waitlist

Source: seo-mcp playbook · curated entry · report an error

Official references

Framework notes

nextjs-app

Inspect rendered URLs, not source files. App Router pages are server-rendered by default, but client components can still hide content from the initial HTML.

wordpress

Check that SEO plugin canonical and noindex settings are not overridden by a page builder template; URL Inspection reflects final HTML, not the plugin UI.

Why this matters

Get the full breakdown

Before you start

How to apply it

Inspect the exact URL

Compare declared and selected canonicals

Extract blocking resources

Get the prompt for your agent

Official references

nextjs-app

wordpress

Related tips