URL is indexed, but ranking work may not stick if Google selected a different canonical.
Last reviewed April 2026 by TheFreeSEOToolKit editorial workflow.
Start with the audit, then confirm Google-side treatment.
Open another workflow if the page needs schema, speed, internal-link, content, or comparison work.
Search Console Inspector
Sign in with your own Google account, choose one of your verified Search Console properties, and inspect how Google is treating a specific URL. This adds the layer a crawler-only audit cannot fully confirm on its own: indexing treatment, canonical handling, crawl state, and the Google-side view of the page.
Connect and inspect
Use your own verified Search Console property, then inspect the exact page you care about.
Read-only Google access TheFreeSEOToolKit only requests Search Console read-only access. We use it to list your verified properties and generate the inspection report you request. We do not edit your Search Console settings, submit sitemaps, or make changes to your Google account. Read the Google data access note.
Checking Search Console connection...
Recent URLs from this property
The dropdown uses recent Search Console performance data, so it is cleaner than typing URLs manually and helps prevent inspecting the wrong property.
Loading URLs...
Inspect a URL that is not in the dropdown
Use this for new pages, low-impression pages, or URLs that have not appeared in Search Console performance data yet.
Recommended inspection queue
Start with these URLs first based on impressions, CTR, and average position.
Recent inspections
Jump back to recently inspected URLs from this browser session.
Inspection result
Recommended next actions
Detail review
What an inspection report can show
Google-selected canonical matches the submitted page, so content and internal links become the next focus.
Review indexing blockers first, then compare against the live SEO audit and improve page-level issues.
How to read this tool
It can use read-only Google access to show property URLs, inspection states, canonicals, and next actions.
Indexing does not mean the page is good enough to rank. Content quality, links, and competition still matter.
Domain properties can be confusing. Confirm the inspected URL belongs to the selected verified property.
Search Console Inspector FAQs
Why can this differ from the SEO audit?
The audit checks the live page. Search Console shows Google-side treatment, such as indexing state and selected canonical.
Can this change my Search Console account?
No. The tool requests read-only access so it can inspect and report, not edit settings or submit changes.
How this tool fits into a stronger site workflow
Search Console Inspector is designed for connecting Search Console data with page-level SEO diagnosis. It is most useful when you run it on a real page, review the output manually, and then connect the result to a concrete fix rather than treating the score or checklist as the whole job.
The page around a tool matters too. A useful tool page should explain what the tool checks, what it cannot know, and what a user should do after the result. That supporting context helps the page feel complete and practical instead of purely functional.
What this page helps check
- property connection
- indexing state
- URL inspection context
- audit fallback signals
Important limitation
It depends on your Search Console access and Google's API response. If data is unavailable, use the fallback audit and verify important URLs directly in Search Console.
Recommended next steps
Use the main SEO audit to compare this result with broader metadata, content, technical, link, and performance signals.
Check the page as a visitor would. Clear copy, visible trust information, and useful next steps still matter.
How to judge the result responsibly
Use Search Console Inspector as a decision-support tool, not as an automatic verdict. The best workflow is to run the check, read the explanation, inspect the page manually, and then decide whether the recommendation makes sense for that page type.
A homepage, guide, service page, and tool page should not all be judged in exactly the same way. A useful result considers the purpose of the page, the amount of supporting content users need, whether trust information is easy to find, and whether the next action is clear.
After making changes, rerun the relevant check and compare the result with the earlier version. That before-and-after habit makes improvements easier to prove and helps avoid changing pages only because a single metric moved.