Repository navigation
Fix copyright year, @id-linked FAQ questions, and soft-404 auxiliary files - #83
Merged
Merged
Conversation
…files - Content Freshness reads the copyright year only from a copyright notice (a year after ©, "copyright" or "(c)", or just before ©), site footer first, so "founded in 2018" no longer beats a footer's "© 2026". - Schema Completeness follows JSON-LD @id references for FAQ questions, accepted answers and HowTo steps, and evaluates an FAQPage or HowTo inside @graph once instead of twice. - llms.txt, llms-full.txt, robots.txt and sitemap.xml that answer 2xx with an HTML page (a redirect to a 404 page, an SPA shell) are reported missing as soft 404s in single-page audits, sitemap audits and crawls. - Bump to 7.4.2 with a CHANGELOG entry and a docs/cli.md note. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The skill ran `npx @canonry/aeo-audit@7.4.0`, so every release needed a manual SKILL.md bump and ClawHub republish, and 7.4.1 never reached skill users. `@7` resolves to the newest 7.x on each run while still avoiding the `@latest` tag that ClawHub flags as a supply-chain risk. CLAUDE.md's examples still said `@4`; they now name the current major and say not to pin an exact version. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
CLAUDE.md described ClawHub publishing as a manual step after editing SKILL.md, but publish.yml already runs `clawhub publish skills/aeo` after the npm publish whenever a version bump lands on main. Describe that, and keep the manual command only as a fallback for a failed workflow. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Content Freshness now reads the copyright year only from a copyright notice (a year after ©, "copyright" or "(c)", or just before ©), checking the site footer first, so text like "founded in 2018" no longer overrides a footer's "© 2026". Schema Completeness follows JSON-LD
@idreferences for FAQ questions, accepted answers and HowTo steps (the way Yoast writes them), and an FAQPage or HowTo inside@graphis no longer evaluated and scored twice./llms.txt,/llms-full.txt,/robots.txtand/sitemap.xmlthat answer 2xx with an HTML page (a redirect to the 404 page, an SPA shell) are now reported missing as soft 404s in single-page audits, sitemap audits and crawls, using a linear-time check and a finding that names the URL and any redirect. Bumps the version to 7.4.2 with a CHANGELOG entry, adocs/cli.mdnote and 40 new tests, and switches theaeoskill from the exact@7.4.0pin to@7so it picks up every 7.x release without a skill update (CLAUDE.md's pin and ClawHub publishing guidance updated to match).🤖 Generated with Claude Code