Exercise 3: Confirming Whether the Finding 1 Fix Actually Worked — Possible Solution ==================================================================== THE SPECIFIC TOOL THIS COURSE ALREADY NAMED FOR THIS ------------------------------ Per seo1-9, the Coverage report in Google Search Console shows "which pages are indexed, and why others were excluded." This is the direct tool for confirming what actually happened to a set of pages from the search engine's own side, as opposed to just trusting that a fix was implemented correctly. WHAT TO ACTUALLY CHECK AFTER FIXING FINDING 1 ------------------------------ Once the ~300 kanji/kana pages are either linked from the main navigation, added to a submitted sitemap, or both (per Exercise 1's own reasoning), the concrete next step is submitting the site (and its new sitemap, if used) to Search Console and then watching the Coverage report specifically for these previously-orphaned URLs — do they begin appearing as "Indexed," or do they show up under an exclusion reason, and if so, which one? WHY THIS IS THE RIGHT KIND OF CHECK, PER seo1-9's OWN REASONING ------------------------------ Per seo1-9, "the Coverage report is where the actual, real-world result of those choices becomes visible" — exactly the same logic Exercise 1 in seo1-9's own chapter established for robots.txt/sitemap/ noindex choices generally. Fixing Finding 1 is itself a change to seo1-5's own crawling/indexing inputs (adding sitemap entries, adding links); the Coverage report is the corresponding output-side confirmation for exactly that kind of change. HOW LONG IT WOULD BE REASONABLE TO WAIT ------------------------------ Per seo1-9's own warn-box, "a meaningful ranking change from real on-page or content work typically takes weeks to months to show up, not days." While indexing status itself (as opposed to full ranking impact) can sometimes update somewhat faster than full ranking signals, per this chapter's own broader "SEO is slow" framing, it would be unreasonable to check once and conclude failure after only a day or two. A period of at least several weeks, with periodic rechecking rather than one single check, matches the structural timeline seo1-9 already established for this whole pipeline. WHY THIS WORKS AS AN ANSWER ------------------------------ It names the specific real tool (Search Console's Coverage report) and specific data (indexed status and exclusion reasons for the previously-orphaned URLs) that would confirm the fix, and applies seo1-9's own "SEO is slow" timeline directly to set a realistic expectation for how long to wait before checking.