Results for “page-audit”

Use this skill for local SEO, location pages, entity consistency, business profiles, NAP quality. Trigger when the task involves seo work related to Local SEO Entity Pages, production implementation, audits, debugging, strategy, or validation.

Use this skill for template SEO pages, data quality, index controls, duplicate prevention, scalable content QA. Trigger when the task involves seo work related to Programmatic SEO Pages, production implementation, audits, debugging, strategy, or validation.

Audits a page or component against the Digital Curator design spec and movemental conventions, checking visual quality, accessibility, token compliance, and consistency before shipping.

Audit AEM Edge Delivery Services pages for content quality, SEO, accessibility, performance, and EDS best practices, producing a prioritized fix list with remediation steps.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

Automated WCAG 2.2 accessibility audit using playwright-cli to crawl every page, inject axe-core via eval, test keyboard navigation, check color contrast, ARIA labels, and heading order. Use when "audit accessibility", "check a11y", "WCAG audit", "check keyboard nav", or "test screen reader".

Audit AEM Edge Delivery Services commerce product pages for search engine crawlability and indexing, then remediate issues with meta tags, structured data, canonical URLs, and image optimization.

Audits codebases, pages, or documents for AI-generated design and copy tells, then proposes surgical fixes for user approval.

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

Improves search engine visibility through technical SEO, on-page optimization, and structured data, following Lighthouse audits and Google guidelines.

Audit a page for internationalization readiness — layout breaks under long translations (pseudo-localization), RTL rendering issues, hardcoded UI strings, and missing lang/dir attributes. Playwright MCP only, no signup.

Audits and improves search visibility through technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.

Audits a wiki for contradictions, stale content, orphan pages, duplicates, missing sections, broken wikilinks, and AI-tell contamination, producing a lint report for human review.

Audit-and-fix linearized mobile layouts at every breakpoint — desktop is not a wide phone. Use when "responsive audit", desktop looks stacked/stretched, no max-width, breakpoint gaps, or 1440 looks like a phone. Distinct from design-mobile-first (touch/mobile-up) and audit-ux-journeys (cross-page IA).

Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.

Audits and improves search visibility through technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.

Performs deterministic, LLM-first SEO audits for websites, blog posts, and GitHub repositories, producing prioritized, confidence-labeled fixes.

Audits and improves search visibility through technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.

Audit a page's weight against a performance budget — total transfer bytes, request count, render-blocking JS/CSS, and oversized or uncompressed images. Produces a pass/fail budget report. Playwright MCP only, no signup.

Runs a full website SEO audit by crawling up to 500 pages, detecting business type, delegating to specialist subagents, and producing a prioritized action plan with a health score.

Audits a research knowledge base for stale profiles, thesis drift, and orphan pages, returning a 0-100 health score with actionable recommendations.

Audits components and pages for WCAG 2.2 AA accessibility issues and applies practical fixes for touch targets, focus states, contrast, labels, and reduced motion.

Validate an AEM Edge Delivery Services sitemap.xml against actual site content, checking URL reachability, lastmod dates, and identifying missing or orphaned pages.

Audits components and pages for WCAG 2.2 AA accessibility issues and applies practical code fixes for touch targets, focus states, contrast, labels, and reduced motion.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Use when the user asks to audit, review, critique, or "make sure it looks right" on a deployed web page, component, or Figma mockup — or when they mention visual issues, CRO, conversion rate, design consistency, accessibility, "feels off", "looks bad", "make it pop", "looks like AI slop". Triggers on keywords like "audit the page", "review the design", "what's wrong with this UI", "CRO audit", "a11y check", "visual hierarchy", "typography check", "does this look right". Activation also recommended after any significant frontend change on gotcontext.ai before calling the work done.

Runs a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO, orchestrating specialized sub-skills and subagents.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

Audit a StyleSeed-based component or page for WCAG 2.2 AA issues and apply practical accessibility fixes where the code makes them safe.