Why isn’t my page showing up?
Help a made-up recipe site decide which pages belong in Google and what to check next.
2K pages not indexed
CheckMyTap, report of Oct 22, 2026
- Discovered - currently not indexed1.1K
- Crawled - currently not indexed521
- Not found (404)228
- Excluded by ‘noindex’ tag148
and 3 more reasons in the same report
Search Console Page indexing report, CheckMyTap; data through Oct 22, 2026.Not every hole in the stack got there the same way.
What would you recommend?
Read the reports, choose an action, then explain your reasoning. Use the analysis prompt and worked answer to check your thinking.
Fictional practice data. K means thousand. Not results from my sites or clients.
Difficulty
Beginner: Keep the useful destination
A fictional recipe website moved a soup recipe to a new URL. A redirect sends someone who opens the old link to the new recipe. The owner wants to know why Google does not index both. Indexed means Google has included the URL in its search index; it does not guarantee that someone sees it.
Decide which URL you want Google to index: the old URL or the current recipe.
Check the source evidence
| URL | What happens | Search report |
|---|---|---|
| Old soup URL | Sends visitors to the current soup recipe. | Not indexed: page with redirect |
| Current soup URL | Shows the current recipe. | Indexed |
Analyze the reports
Download the reports and attach them to your AI tool. Paste the analysis prompt, then check its answer against the evidence.
Read or select the prompt
Then check its work. Check the reporting periods, one important source row and any calculation. Does its recommendation actually follow from that evidence?
Help checking the analysis
- Download the complete case and give it to an AI tool with the analysis prompt.
- Ask AI to organize the evidence. Check the dates, one important row and any calculation it uses.
- Choose or reject its recommendation. Explain the page action you would take and what you would check next.
If you’re stuck: Which URL should show the recipe, and which should take someone there?
Explain your decision
Use the evidence to explain your choice and next check. Your writing is not submitted or graded.
Name the intended destination and how you would check it.
Explain which address contains the current recipe.
Explain how old links can keep helping visitors.
Compare with a worked answer
Does not fit this case: Restore a copy at the old URL so that both addresses can be indexed.
The old address is supposed to send people to the replacement. Restoring a second copy changes that plan without a distinct reader need.
Fits this case: Keep the redirect and check that the destination shows the correct current recipe.
The exclusion is consistent with the old URL’s purpose. The destination, rather than the old address, is the useful page to check.
Does not fit this case: Delete the old URL because the current recipe is already in Google’s index.
The current recipe being indexed does not make its old incoming links unnecessary. Removing the working route can break those links instead of preserving the intended journey.
How I would approach it
I would open the old link, confirm it reaches the right current recipe and keep that redirect.
What we still don’t know
The report does not show that every old link works. This example only describes the checked pair.
Check your own explanation
- Keep the old-to-current redirect.
- Check the current recipe is the intended destination.
- Do not treat a larger indexed-page percentage as the goal.
Keep your work
Choose an answer and write your reasoning. Compare with the worked answer.
Notes are not saved automatically. Download your notes before leaving.
Intermediate: Choose the URL that needs attention
A fictional recipe site has three reported exclusions. A canonical tells a search engine which URL is preferred for similar content. These checks describe individual examples, not every page on the site.
Look at what each URL is for before deciding whether its indexing status needs a fix.
Check the source evidence
| Example URL | Search Console reason | Live check | Intended treatment |
|---|---|---|---|
| /old-soup/ | Page with redirect | 301 redirect to /soup/; destination returns 200. | Keep the move. |
| /lentil-stew/ | Discovered, not indexed | 200; crawling allowed; self-canonical. Missing from the recipe-category links. | A current recipe readers should be able to find. |
| /soup/?servings=4 | Crawled, not indexed | 200; same recipe with a servings setting; canonical points to /soup/. | Keep one preferred recipe URL. |
Analyze the reports
Download the reports and attach them to your AI tool. Paste the analysis prompt, then check its answer against the evidence.
Read or select the prompt
Then check its work. Check the reporting periods, one important source row and any calculation. Does its recommendation actually follow from that evidence?
Help checking the analysis
- Download the complete case and give it to an AI tool with the analysis prompt.
- Ask AI to organize the evidence. Check the dates, one important row and any calculation it uses.
- Choose or reject its recommendation. Explain the page action you would take and what you would check next.
If you’re stuck: Separate the current recipe from the old address and the same-recipe variation.
Explain your decision
Use the evidence to explain your choice and next check. Your writing is not submitted or graded.
For all three, choose leave, investigate or change and give a reason.
Use the destination, category links or preferred recipe URL as appropriate.
Separate a navigation repair from whether Google later crawls or indexes a page.
Compare with a worked answer
Does not fit this case: Make the servings URL self-canonical so that the excluded variation can compete as another recipe page.
This packet says it is the same recipe with a setting, and one preferred recipe URL is intentional. Changing the canonical does not address the missing current recipe.
Partly right: Request indexing for the lentil-stew URL, then wait before making any navigation change.
An individual request may be a later step, but it leaves the observed navigation gap in place. The report also does not guarantee that a request will result in indexing.
How I would approach it
I would confirm that lentil stew belongs in that category and add its ordinary link. I would leave the checked redirect and variation canonical in place, then monitor crawling and indexing separately.
What we still don’t know
The missing category link does not prove why Google has not indexed the recipe; there may be other paths and other barriers.
Another approach worth considering
A different current recipe with a demonstrated access failure could take priority. No such failure is supplied in this packet.
What would change my mind
If lentil stew is intentionally unpublished, irrelevant to the category or already linked elsewhere in an appropriate route, I would revisit the navigation change.
Check your own explanation
- Distinguish a moved URL, a current recipe and a servings variation.
- Preserve intentional redirects and canonicals.
- Investigate the current recipe’s category omission without claiming it caused non-indexing.
- Name a later crawl/indexing check separately from the navigation repair.
Keep your work
Choose an answer and write your reasoning. Compare with the worked answer.
Notes are not saved automatically. Download your notes before leaving.
Advanced practice: Repair navigation without undoing URL policy
A fictional recipe publisher must restore recipe-category navigation before tomorrow’s campaign. One frontend developer has three hours. The owner wants every excluded URL submitted for indexing, but the release goal is working ordinary links, including when JavaScript is unavailable. Current redirect and canonical policies are intentional.
Use the URL evidence and markup to find a template problem worth fixing within the time available. This is a written exercise; the sample is not a working website.
Check the source evidence
| Sample group | URLs checked | Category and URL checks |
|---|---|---|
| Current recipes, new category template | 4 | 200, allowed and self-canonical; category source uses buttons with data-url, not href links. Buttons work with JavaScript; no destination link works there without it. |
| Current recipes, old category template | 2 | 200, allowed and self-canonical; ordinary href links work with and without JavaScript. |
| Servings variations | 2 | Same recipe as the preferred base URL; canonical points to base as intended. |
| Old moved URLs | 2 | 301 to intended current recipe; each destination returns 200. |
Download the fictional URL and template checks (CSV)Ten individual URL checks. Use both the search report and the live/source observations; one does not replace the other.
| Possible work | Estimate |
|---|---|
| Replace destination buttons with ordinary anchors while keeping the enhanced behavior. | 1 hour plus 1 hour of regression checks. |
| Prepare individual indexing requests for the four current recipe URLs. | 1 hour; no change to the category controls. |
| Review and rewrite two recipe bodies. | 3 hours; no demonstrated body-content fault in this sample. |
Analyze the reports
Download the reports and attach them to your AI tool. Paste the analysis prompt, then check its answer against the evidence.
Read or select the prompt
Then check its work. Check the source periods, a decisive row and any calculation. Challenge its strongest assumption and ask what would reverse the recommendation.
Help checking the analysis
- Download the complete case and give it to an AI tool with the analysis prompt.
- Ask AI to organize the evidence. Check the dates, one important row and any calculation it uses.
- Choose or reject its recommendation. Explain the page action you would take and what you would check next.
If you’re stuck: The brief is about a specific release behavior, not reaching an indexed percentage. Compare the four new-template rows with the two old-template controls.
Explain your decision
Use the evidence to explain your choice and next check. Your writing is not submitted or graded.
Account for each URL; you can group them if you name the members and shared reason.
Show the proposed HTML and explain how it supports the intended navigation.
Include JavaScript on/off, keyboard use, destinations and checks that intentional redirects and canonicals still work.
Name when and where you would check; keep this separate from proving navigation works.
Compare with a worked answer
Partly right: Submit the four current URLs for indexing and use the remaining time to watch their search status.
Those are the current pages to monitor, but requests leave the demonstrated non-JavaScript navigation failure unresolved. This does not meet the stated release goal.
Fits this case: Replace the new template’s destination buttons with href links, test the sampled routes and preserve the redirect and canonical policies.
The source and browser checks isolate a reproducible template-level navigation defect. An ordinary anchor addresses that release goal within two of the available three hours, without reviving old or duplicate URLs.
Does not fit this case: Give the servings variations their own canonicals and rewrite those recipe copies before requesting another crawl.
The packet says the variations are the same recipe and the base canonical is intentional. This changes a policy that is working as intended and leaves the category control failure untouched.
How I would approach it
I would replace destination buttons with ordinary links using each recipe’s existing URL, retaining optional enhancement. I would check all four affected destinations with and without JavaScript, keyboard activation and open-in-new-tab behavior. Then I would spot-check the two working controls, the old redirects and the variation canonicals. Crawling and indexing would be later observations, not release promises.
What we still don’t know
The sample establishes the navigation behavior on these routes. It does not prove that the template caused the reported non-indexing or that repairing links will make Google index every recipe.
Another approach worth considering
If the campaign is canceled but an important current recipe has a separately reproduced server-access failure, an access fix could take priority under a new brief. That condition is absent here.
What would change my mind
If the category source already contains working href destinations, or the control is an action rather than navigation, I would revisit the proposed markup change.
The markup change
Before
<button data-url="/recipes/lentil-stew/">Lentil stew</button>After
<a href="/recipes/lentil-stew/">Lentil stew</a>Check your own explanation
- Specify reproduction and verification steps for the four reported new-template states, using the two working links as comparisons.
- Use an anchor href for destination navigation; do not change same-recipe canonicals or old redirects.
- Keep the implementation and regression plan within three hours.
- Include no-JavaScript, keyboard, destination-status and unaffected-policy regression checks.
- Separate the verified navigation outcome from any later Google crawling or indexing outcome.
Keep your work
Choose an answer and write your reasoning. Compare with the worked answer.
Notes are not saved automatically. Download your notes before leaving.
Something wrong, or a different approach? Include your evidence and lesson link. Leave out private information.
Optional: explore a worked real report
Use this as a reference when checking your analysis. You do not need to complete a second set of notes.
A site owner wants every page indexed. Would you agree?
You have one session to investigate whether CheckMyTap needs indexing work. Compare its report with three other real reports from my own sites, then recommend what to inspect before anyone starts rewriting, deleting pages or requesting indexing. This assignment sets the priority; the counts do not tell you which site matters most.
Indexed means Google has put a page in its search index, making it eligible to appear in results. It does not guarantee a good position or clicks. “Not indexed” includes several different situations, some intentional.
| Site | Indexed | Not indexed |
|---|---|---|
| RatingPlate | 45 | 3 |
| CheckMyTap | 191 | 2K |
| UpOrbit | 76 | 267 |
| The Quack Report | 146 | 22 |
See why each answer is right or wrong
Not quiteCheckMyTap needs the most pages deleted because it has the largest not-indexed count.The size of the bucket does not tell you which pages are useful or why they were left out. Deleting pages without reading them could remove answers people need.
CorrectRead the reasons and check which pages should be indexed before choosing a fix.A redirect, an intentionally excluded page and an important page Google has not crawled need different decisions. The totals help you choose questions; they do not supply the answers.
Not quiteRequest indexing for every unindexed page in these example reports.Some pages should remain out of the index. A request also does not resolve an unwanted redirect, a blocked page or a page that does not answer a useful question.
RatingPlate: a small bucket with a specific explanation
RatingPlate’s export lists 45 indexed pages and 3 unindexed pages. All the unindexed pages are reported as “Page with redirect”: their URLs send visitors elsewhere. The export does not name the URLs or their destinations.
See why each answer is right or wrong
Not quiteRemove the redirects so the original URLs can be indexed.That could undo an intentional move. You first need to know what each original URL represents and whether its destination is the page people should reach.
CorrectCheck that the redirects are intended, then inspect the destination pages.An old URL that correctly sends people to its replacement is not automatically a defect. If the destination is wrong, fix the route; if the replacement should appear in search, inspect that destination’s status.
Not quiteThe report proves the whole site has no search problems.It explains one bucket, not the site’s search performance. An indexed page can still appear rarely, answer the wrong question or fail to attract clicks.
This is a check to make, not a claim that the redirects are correct. The summary export cannot establish that. For the separate question of whether an indexed page reaches searchers, use the search performance report.
CheckMyTap: the same label hides several decisions
CheckMyTap helps people look up water-quality information. Its report contains 2K unindexed pages. Read the breakdown before deciding what that number means.
| Reported reason | Pages |
|---|---|
| Not found (404) | 228 |
| Excluded by ‘noindex’ tag | 148 |
| Blocked by robots.txt | 6 |
| Page with redirect | 6 |
| Discovered - currently not indexed | 1.1K |
| Crawled - currently not indexed | 521 |
| Duplicate, Google chose different canonical than user | 1 |
“Discovered” means Google knows about a URL but has not crawled it yet. “Crawled” means Google fetched the page; this group has not been added to the index.
See why each answer is right or wrong
CorrectInspect important pages from the discovered and crawled groups, and check whether the other exclusions are intended.Choose pages the site actually wants people to find. Check their links, crawl access, index status and content before recommending technical work, an update or removal. The summary does not identify which pages need which action.
Not quiteDelete every crawled-but-unindexed page; Google has already rejected its content.The status does not establish that a page is poor or should be deleted. You have not seen the URLs, their content or the reasons behind the status.
Partly rightLeave everything alone until the whole report improves.Some pages may only need time, but waiting without checking important pages could leave an accidental block or a broken route unresolved. Name what you will inspect and when you will check again.
Read the video explanation
Different reasons need different checks.
Check whether the redirect is intended.
Investigate important uncrawled pages separately.
Understand the labels and choose a next action
An important page is blocked by mistake. If its live page has an unintended noindex instruction or crawl restriction, correct that setting, test the page again and check its status later. Keep an intentional restriction when the page should remain out of search.
An old URL redirects. If it sends people to the intended replacement, keep the redirect and inspect the replacement. If it sends them somewhere unrelated, correct the destination.
Google knows a useful page but has not crawled it. Check whether relevant pages link to it and whether it belongs in the sitemap. Add missing routes where appropriate, then monitor crawling. A link or sitemap entry does not guarantee indexing.
Google crawled a page but left it out. Inspect the recorded and live page, the preferred URL and what the content answers. Fix an identified technical problem; improve a missing answer; consider combining overlapping pages only after confirming they serve the same need. The report label alone does not choose among those actions.
A 404 means the page was not found. A noindex instruction asks search engines not to index a page. Robots.txt can restrict crawling. A canonical is a preferred version of a page; Google may choose a different version. Each can reflect an intentional choice or an accident, so inspect examples rather than treating the label as the diagnosis.
Review the change: did a smaller count mean improvement?
| Report date | Indexed | Not indexed | Known total |
|---|---|---|---|
| 2026-09-20 | 252 | 2.3K | 2.5K |
| 2026-10-22 | 191 | 2K | 2.2K |
See why each answer is right or wrong
Not quiteThe lower not-indexed count proves the indexing work succeeded.The indexed count also fell. Some URLs disappeared from this report’s known total; the summary does not say which ones or why. A smaller excluded bucket is not proof that more important pages became indexed.
Not quiteThe lower indexed count proves the site lost valuable search traffic.The report does not measure visits or tell you whether the pages that disappeared were useful search destinations. You would need the affected URLs and their performance before making that claim.
CorrectBoth counts fell. Check which important pages changed status before calling it progress or a loss.This is the defensible report: describe the two movements, then investigate the pages behind them. Keep intentional removals separate from pages that still need to be found.
Now apply the distinction to your own site. Start with a page someone needs, not a target percentage. Find its status in URL Inspection, compare Google’s recorded version with the live page where necessary, and decide whether its current treatment is intentional. A successful live test does not guarantee indexing.
These snapshots show movements in the reports, not what caused them. For a related example after a rebuild, check the missing page before treating the whole site.
Your real-report answer review
- Right
- 0
- Partly right
- 0
- Wrong
- 0
- Unanswered
- 0
Use the explanations beside each question to review your choices, then write your recommendation.
Only your latest choice for each real-report question counts. Your written recommendation is not graded.
Review each answer
Write your recommendation
For your assigned CheckMyTap investigation, write the short recommendation you would send to the site owner: what you would inspect, what you would leave alone for now, and which finding would change your action. Your notes stay on this page until you download them; they are not submitted or saved automatically.
Compare with a worked recommendation
For this assigned CheckMyTap session, I would inspect pages the owner wants people to find before recommending deletion or bulk indexing requests. Its October 22, 2026 report shows 2K unindexed pages across different reasons. I would correct an unintended block on an important page, but keep an intended exclusion. For discovered pages, I would check links and crawl access; for crawled pages, I would inspect the preferred URL and the answer before proposing an update or combination. RatingPlate’s 3 redirect rows illustrate why the same fix should not apply everywhere. CheckMyTap’s smaller unindexed total is not proof of improvement because its indexed count fell too. I would track whether the important pages reach the people who need them, rather than treat a smaller excluded count as the goal.
Compare the evidence and next check with your own. If you would choose a different action, explain what supports it.
Ready to build a whole page? Explore the Moat Map course (Free during early access).