Owner's diagnostic guide
Why isn't my website on Google?
First separate two problems: a page that is not indexed, and an indexed page that does not appear for the search you tried. They need different work. Start with the exact service-page URL, not a guess based on one search.
No account or email needed for the first report. Pro is $99/mo for weekly monitoring and up to 10 sites.
What should I fix first?
Work down this list. If a check passes, move on. You do not need another tool or a paid plan to use it.
| What you find | Next action | What to verify |
|---|---|---|
| You do not know whether the page is indexed | Inspect the exact URL in your verified Search Console property | Read the indexed result separately from the live test |
| The page cannot be reached | Check login requirements, server errors, redirects, and accidental crawl blocks | The intended public page loads without signing in |
| The page is excluded or another canonical is selected | Read the reported reason and confirm whether exclusion is intentional | Private pages stay private; the intended public URL is consistent |
| The page is indexed but not found for your search | Review page-level queries and relevance before making another page | Measure impressions and clicks separately from inquiries |
1. Inspect the page, not just the domain
Use URL Inspection in Google Search Console. The indexed result describes what Google has stored; a live test checks present accessibility and eligibility. A passing live test does not mean the page is indexed or will rank.
2. Resolve only unintended exclusions
Investigate the reason shown. A public service page might have an accidental noindex, login wall, crawl block, or failed response. Do not remove protections from customer accounts, private documents, or checkout pages just to increase indexed-page counts.
3. Check which URL should represent the page
If multiple URLs show the same content, inspect the canonical Google selected and the URL you intended. Check redirects, internal links, and sitemap entries for consistency. Do not create copies of the same page to try to force inclusion.
4. Give the useful page a clear path in
Link the page from a relevant public navigation or service overview. Describe the actual service, who it is for, and the next step. These are sensible cleanup actions, not proof that Google will index the page.
5. Request a review after a real fix
After correcting an issue, use the live test and, when available, request indexing. Keep the corrected URL and date in your change log. Repeated requests do not make crawling faster, and a request does not guarantee inclusion.
6. Know what the free audit can tell you
Corpus Plan checks technical website signals and gives you findings to investigate. It cannot confirm Google indexing from those signals alone. Use Search Console for indexing evidence, then use the audit to organize the website work.
Turn the findings into your next steps
- Run the free audit. The report shows SEO, speed, trust, content, and AI-citability findings before signup.
- Claim the workspace. Keep the site, score history, and fix queue in one place.
- Go Pro when monitoring matters. Pro adds weekly re-scans, alerts, generated GEO files, grounded drafts, and traffic context.
Sources and limits
Guidance checked 2026-09-06. Search engines decide indexing and rankings; a checklist cannot guarantee either.
- Google: inspect and troubleshoot a single page
- Google: URL Inspection tool
- Google: requesting a recrawl and its limits
Choose your next website check
- Search basics: Investigate a page missing from Google, then prioritize your SEO fixes.
- Business information: Check your schema and use the schema review checklist.
- AI search: Understand SEO versus GEO, check crawler access, and read what llms.txt can and cannot do.
- Customer inquiries: Test the path from a visit to an inquiry.
Corpus Plan does not promise rankings, traffic, revenue, or AI mentions. It shows what the checks found and keeps the fix work organized.