Review author information in structured data, a machine-readable description of page content. Check names, profile links, and connections to articles or pages, then identify corrections using the rendered HTML and HTTP response.
Use when auditing metadata, crawlability, structured data, or indexability related to Implement comprehensive author markup. Verify the rendered HTML and HTTP response rather than relying only on source files.
Run score Not tested
See how to installauthor-info helps review and correct author information in structured data that search engines can read. It checks Person or Organization information written in JSON-LD, including properties such as name, url, sameAs, and jobTitle.
It also reviews how that information connects to the author property of an Article or WebPage, so the author details are associated with the relevant content.
Use it when you want to identify an article’s author or connect information on your website with the author’s external profiles. During code review, it identifies the paths or templates of affected pages and describes how to check the output after corrections have been made.
Person data to the article’s author property.”sameAs means.”The review requires checking the actual rendered HTML and HTTP response, as well as the source files.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Structured author information helps search engines uniquely identify authors across the web, building an authority profile that can benefit your site's rankings.
name, url, sameAs, and jobTitleArticle or WebPage schemaVerify that the page includes structured data identifying the author with relevant metadata.
Add a Person or Organization schema to your JSON-LD block and link it to the author property of your content.
Explain how 'sameAs' properties in schema help search engines connect an author to their other authoritative profiles.
Review metadata generation, rendered HTML, structured data, and response headers related to Implement comprehensive author markup. 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/author-info
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.