Repository navigation
SEO: verify live indexable HTML for 12 official GSC Toolify inspection URLs - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Source-backed read-only diagnosis after 2026-10-26 official Google URL Inspection. All 12 fixed URL targets are currently intended indexable according to Toolify
CORE_TOOLS_BY_DEMAND+ locale-specificINDEX_EXCEPTIONS(en4, ja2, th/ru/tr/ar/fr/es 6). Google retains 8Crawled - currently not indexedrecords and 4 historicalExcluded by noindexrecords from July, although October policy intends those 4 indexable. Rather than indiscriminately changing noindex rules, this PR adds precise live HTTP 200/redirect/canonical/robots meta/X-Robots-Tag assertions, comparing source intent vs public HTML on the 12 chosen URLs. Runs after merge or manually. Handles Google-cached verdict separately; no indexing requests, robots/canonical edits, VPS deployment, credentials or new expensive recurring schedule. Includes no-network contract test. If public noindex/incorrect canonical is found, treat as actual VPS deployment incident; if live 12/12 PASS, monitor GSC recrawl and content usefulness separately.