Audit important pages for settings that hide descriptions in Google search results. Check robots meta tags and response headers, report affected URLs, and adjust snippet controls after confirming whether the restriction is intentional.
Use when auditing robots meta tags. Applies to any important landing page, article, or product page that should appear with a description in search results.
This skill checks important pages for settings that hide their descriptions in Google search results. It examines <meta name='robots'> and the X-Robots-Tag response header for nosnippet and max-snippet:0. It also helps create a report listing affected URLs, their page types, and whether hiding descriptions is intentional.
Use it to review landing pages, articles, and product pages that should have descriptions in search results. It can help investigate why a result shows only a title and URL, or review robots settings across multiple pages. The review explains the directives that prevent descriptions from appearing and how those settings can be changed.
nosnippet and max-snippet:0.”nosnippet or changing it to max-snippet:-1 to allow descriptions.”The skill confirms whether hiding descriptions is intentional before making changes. The source gives legally sensitive content as an example where nosnippet may be used deliberately.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. 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.
Pages with nosnippet display without a description in search results, reducing click-through rates and making it harder for users to understand whether the result is relevant to their query.
Check the <meta name='robots'> tag and X-Robots-Tag response header for each important page. Flag any that contain 'nosnippet' or 'max-snippet:0'. Confirm these pages intentionally suppress snippets.
Remove 'nosnippet' from the <meta name='robots'> content attribute on important pages. Replace with 'max-snippet:-1' to explicitly allow full-length snippets, or simply omit snippet directives to use the default (allowed).
The nosnippet directive tells Google not to display a text snippet (description) for your page in search results. Without a snippet, users see only the page title and URL—this reduces click-through rates and is rarely the intended behaviour for content pages.
Check all pages for <meta name='robots' content='...'> tags. Parse the content value and flag any that include 'nosnippet' or 'max-snippet:0'. Generate a report of affected URLs, their page type, and whether the nosnippet directive is intentional. Also check X-Robots-Tag response headers.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
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.