Review a website’s contact page for working contact methods and easy access from other pages. Add relevant contact information or forms, and inspect rendered HTML and HTTP responses to check the final page.
Use when auditing metadata, crawlability, structured data, or indexability related to Create a comprehensive Contact page. Verify the rendered HTML and HTTP response rather than relying only on source files.
Run score Not tested
See how to installChecks whether a contact page has the necessary contact details and is easy to find from other pages. It reviews whether multiple contact methods, such as email, phone, and a contact form, actually work. Where needed, it helps create a /contact page or add contact information. A physical address and map are also reviewed when appropriate for the business.
Use it when creating a contact page for a business website or reviewing contact information on a published site. It helps check whether visitors can reach the contact details and whether the output presented to search engines has problems, alongside checking that the page exists.
/contact.”The checks require rendered HTML and HTTP responses, alongside source files. Whether to include an address or map depends on the website’s business.
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.
A clear and accessible contact page is a major trust signal for E-E-A-T and provides essential support for users, improving overall site credibility.
Verify that the website has a dedicated Contact page with multiple, working contact methods.
Create a /contact page and add a contact form, email address, and other relevant contact information.
Explain why having a verifiable contact page is a critical factor for business legitimacy and search rankings.
Review metadata generation, rendered HTML, structured data, and response headers related to Create a comprehensive Contact page. 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/contact-page
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.