Index of every page on this site: llms.txt
All skills
coreyhaines31 avatar

/seo-audit

@5b2b400
Run it yourself

When the user wants to audit or diagnose SEO, or asks why traffic dropped, a page won't rank, or whether a setup like canonicals, hreflang, or redirects is right: technical SEO, indexing, Google updates, on-page and titles, Core Web Vitals, local SEO. Start here when someone just says their SEO is bad. For pages at scale, see programmatic-seo. For structured data, see schema. For AI search, see ai-seo.

Use this Skill: https://skilld.dev/gh/coreyhaines31/marketingskills/seo-audit

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referenceslocal-seo-pages-and-measurement.md

≈1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Location Pages and Measurement

Use this when the request includes local pages, schema, or performance reporting.

Page Content That Helps a Local Customer

For a real customer-facing location, include accurate location/contact details, hours, services available there, booking/call links, access/parking directions where known, staff or location evidence, and useful nearby/service information. Link it from a location index and relevant service pages.

For service coverage without an office, explain actual availability, constraints, travel or call-out policies, relevant local work examples when available, and a clear enquiry path. Say that it is a service area. Do not show a fake street address or imply a staffed branch.

Example decision: a plumber has one operating base and serves two nearby towns. One honest coverage page may suffice. Separate town pages are justified only by additional useful information or evidence; neither town automatically merits another Business Profile.

Before scaling, confirm a stable data source and meaningful differences across pages. Check the current doorway-abuse policy. Route justified templates to programmatic-seo and hierarchy to site-architecture; consolidate pages when the proposed variants add no value.

Local Structured Data

Use the most specific accurate LocalBusiness subtype and a stable identifier for each real location. Match the visible page facts; connect the location URL, public phone, hours, and physical coordinates where applicable. Do not mark service cities as invented branches or publish a hidden residential address through JSON-LD.

Important distinction: Schema.org can describe a business without satisfying Google's rich-result requirements. Google's LocalBusiness documentation requires an address for that search feature. For a business that cannot publish one, preserve privacy and explain that the rich-result requirement is unmet; do not fabricate an address or promise eligibility from areaServed alone.

Self-serving LocalBusiness review markup does not earn review stars merely because the business displays testimonials. Do not import a profile rating into markup as a shortcut to stars.

Use schema for implementation. Validate the rendered page and relevant test tools, then verify deployed markup matches the public content. A stripped text fetch is insufficient proof that JavaScript-injected JSON-LD is absent. Validation does not guarantee display or a local-pack ranking change.

Measure Customer Outcomes

Keep a baseline by location and period:

Metric Evidence Interpretation limits
Qualified calls/bookings/leads CRM or owner-confirmed outcomes Deduplicate; attribution may be incomplete
Profile interactions Available Business Profile performance export Interaction is not a completed sale
Organic local queries/pages Search Console query/page reports Privacy thresholds and aggregation limit detail
Website actions from profile links Analytics with consistent campaign tags Consent, blockers, and tagging can affect counts
Local visibility Comparable query/location observations Distance, personalization, and volatility matter

Use a consistent tagging convention for profile website links while keeping the canonical location URL stable. Test that redirects and booking flows preserve the attribution needed. For call tracking, retain a genuine reachable business contact and verify the platform's current phone rules; do not blindly replace canonical citation numbers.

Review changes against a comparable period, seasonality, opening-hours changes, and service capacity. Record what changed and when. Treat a visibility increase as an observation, not proof of causation or additional revenue. Set follow-up timing with the user rather than promising a universal recovery deadline.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warningtoday5 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill provides a technical SEO audit framework for diagnosing site performance. It includes specific security instructions to prevent the agent from following malicious commands found on external websites during audits. No malicious code or suspicious behaviors were detected.

  • Sockettoday

    No alerts

  • Snyktoday

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    2 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 5b2b400. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
metadata
{
  "version": "2.2.9"
}
  • SEO
  • technical-seo
  • audit
  • on-page
  • crawlability
  • indexation
  • core-web-vitals
  • mobile-friendly
  • schema-markup

README badge

README badge for coreyhaines31/marketingskills/seo-audit

Diagnoses SEO problems on websites by checking crawlability, indexation, speed, mobile-friendliness, on-page elements, and international configurations. The audit walks through technical foundations first, then on-page optimization, and flags common issues like noindex mistakes, canonical conflicts, hreflang errors, and Core Web Vitals problems.

Generated from the current SKILL.md.

Does this skill check for schema markup and structured data?
The skill can identify schema markup issues, but it has a significant limitation: web_fetch and curl cannot reliably detect JSON-LD injected by client-side JavaScript (common in CMS plugins like Yoast or RankMath). For accurate schema detection, use the Google Rich Results Test, browser DevTools, or Screaming Frog instead.
What does this skill prioritize in an audit?
The skill audits in this order: crawlability and indexation, technical foundations (speed, mobile, HTTPS), on-page optimization (titles, headings, content), content quality, and authority/links. It covers robots.txt, XML sitemaps, Core Web Vitals, canonicals, hreflang for multilingual sites, and internal linking.
Does this skill handle international/multilingual sites?
Yes. The skill includes a full international SEO section covering hreflang setup (including self-referencing entries and reciprocal links), canonicalization across locales, locale URL structure, and detection of common errors like cross-locale canonicals or missing x-default entries.
Does this skill require Search Console or analytics access?
Access to Google Search Console and analytics is helpful but not strictly required. The skill can perform initial crawlability and on-page checks without it, but Search Console provides the most accurate indexation and coverage reports.
Does this skill work with any CMS or is it platform-agnostic?
The skill is platform-agnostic and addresses common SEO issues across any site type (SaaS, e-commerce, blog). It notes CMS-specific behaviors (like client-side schema injection in plugins) but does not assume a particular platform.

Generated from the current SKILL.md. These answers refresh after source changes.