Audit sitemap pages in schema_audit, not guessed paths - #236
Merged
Merged
Conversation
schema_audit checked a fixed list of common paths. On imagewize.com six of them redirect or 404, and the output listed them as Not Found while also reporting that all pages have schema, which reads as six pages missing schema. Default pages now come from the site's sitemap (wp-sitemap.xml, sitemap_index.xml, sitemap.xml), page sitemaps only when there is an index, capped by a new maxPages parameter (default 25). The common paths remain the fallback for sites without a sitemap. URLs that don't return 200 get their own section with status code and redirect target, worded by where the URL came from, and are never counted toward the schema totals. Each page is now fetched in one request instead of two.
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.
Version:
5.24.2The
schema_auditMCP tool used to check a fixed list of 11 guessed paths, such as/about-us/,/shop/and/news/. Now it audits the pages listed in the site's sitemap, which gives more accurate results. With the old list, sites that lacked some of those paths got misleading output. On imagewize.com, six of the paths redirect or return 404. The report listed them as "Not Found" and still ended with "All pages have schema markup", which reads as six pages missing schema. The old list also never reached the site's real service and landing pages. Pages are now found throughwp-sitemap.xml,sitemap_index.xmlorsitemap.xml, and a newmaxPagescap limits how many are checked. URLs that don't return 200 are reported separately and no longer count toward the schema totals. This release is version 5.24.2.Page Discovery:
pagesis not passed, the page list comes from the sitemap. The tool trieswp-sitemap.xml(WordPress core) first, thensitemap_index.xml(Yoast, Rank Math, The SEO Framework), thensitemap.xml. From a sitemap index it reads only the page sitemaps, when there are any. The homepage is always checked first.maxPagesparameter (default 25) caps how many sitemap URLs are checked. When the cap shortens the list, the output says so, e.g. "first 25 of 177 URLs".Audit Output (
mcp-server/src/server.ts):pagesargument.summarymode, pages without schema are still listed, and so are URLs that did not return 200. The parameter description was updated to match.Documentation:
CHANGELOG.mdgets a 5.24.2 "Fixed" entry. It describes the new sitemap discovery,maxPages, the "Not checked" section and the speedup. It also notes that thewp-ops schema-auditCLI command (wp-cli/seo/schema-audit.sh) still uses the fixed path list.mcp-server/README.mdnow explains howschema_auditbuilds its page list: frompages, from the sitemap, or from the fallback. It also explains how URLs that don't return 200 are reported.Files Changed:
CHANGELOG.md(Modified)mcp-server/README.md(Modified)mcp-server/src/server.ts(Modified)mcp-server/src/tools/schemaAudit.ts(Modified)