Audit canonical URLs, which tell search engines the preferred page address, for redirects. The skill checks rendered HTML and HTTP responses, identifies affected routes or templates, and guides updates that point directly to the final URL returning 200 OK.
Use when auditing metadata, crawlability, structured data, or indexability related to Avoid redirect chains on canonical URLs. Verify the rendered HTML and HTTP response rather than relying only on source files.
Review the instructions the agent will receive before you install.
Canonical chains confuse search engines and can result in the wrong version of a page being indexed, while also adding unnecessary latency for crawlers.
rel="canonical" tag returns a 200 OK statusVerify that the canonical URL of the page does not result in any redirects.
Update the <link rel="canonical"> tag to point directly to the final, non-redirecting URL.
Explain why pointing a canonical tag to a redirecting URL weakens the canonical-url signal and impacts SEO.
Review metadata generation, rendered HTML, structured data, and response headers related to Avoid redirect chains on canonical URLs. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/canonical-chain
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.