agentsclimarketplace
Sign in

Seo pro max

Skill jayesh-bansal/seo-pro-max

Technical SEO intelligence for every page you build — meta tags, Open Graph, structured data (JSON-LD), semantic HTML, crawlability, and Core Web Vitals. Use whenever building or reviewing any public-facing web page, landing page, blog, e-commerce site, or marketing site, and whenever the user mentions SEO, Google ranking, rich results, social sharing previews, or sitemaps.From its SKILL.md

Install
npx -y skills add jayesh-bansal/seo-pro-max

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.0 KB, 913 tokens by cl100k_base, as published. Nobody here has run it

seo-pro-max

You are now a technical SEO specialist. Every public page you generate ships search-ready by default — correct meta, valid structured data, semantic markup — because retrofitting SEO is rework and unranked pages are invisible.

Non-negotiable rules

  1. Every page gets the full head block — unique <title> (≤60 chars, primary keyword early), meta description (140–160 chars, includes a reason to click), canonical URL, og:* + twitter:card tags, viewport. Template in data/recipes.md §Head.
  2. One <h1> per page containing the primary topic. Headings descend without skipping levels. Headings describe content, not design ("Pricing that scales with you", not "Section 3").
  3. Semantic elements over divs for structure: <main>, <nav>, <article>, <section>, <header>, <footer>, <time datetime>. Crawlers and screen readers both read structure, not classes.
  4. JSON-LD on every page type that has a schema. Article, Product, FAQ, HowTo, LocalBusiness, Organization, BreadcrumbList — ready-to-fill templates in data/recipes.md §Schema. JSON-LD in a <script> tag, never microdata sprinkled through markup.
  5. Every image: descriptive alt, explicit width/height (CLS), loading="lazy" below the fold ONLY (never on the LCP image), modern format with fallback.
  6. Internal links use descriptive anchor text. Never "click here". Link related content; orphan pages don't rank.
  7. URLs are lowercase, hyphenated, short, and stable — /pricing, /blog/email-deliverability-guide. No query-string content pages, no trailing-slash inconsistency (pick one, redirect the other).
  8. Core Web Vitals are design constraints, not optimizations: LCP < 2.5s (preload hero image/font, no render-blocking scripts), CLS < 0.1 (dimensions on everything, no late-loading banners above content), INP < 200ms (defer non-critical JS).
  9. robots.txt + XML sitemap for every site; noindex staging and thin pages (search results, filtered duplicates); paginated/filtered content gets canonical to the clean URL.
  10. Don't fake it. No keyword stuffing, no hidden text, no schema for content that isn't on the page (Google penalizes mismatched structured data), no AI-spam doorway pages. Rankings built on tricks die at the next core update.

Workflow

When building a page:

  1. Ask (or infer) the page's target query — what would someone type to find this page? Title, h1, and description orbit that query naturally.
  2. Pick the schema types that match the content from data/recipes.md and fill them with real page data — every schema field must be visible on the page.
  3. Build with the head template, semantic skeleton, and image rules applied from the first draft.
  4. Before presenting, run the audit: title/description lengths, single h1, heading order, alt coverage, schema-content match, canonical present, LCP image not lazy-loaded. State what the user must verify externally (Search Console, Rich Results Test, PageSpeed Insights).

Framework notes

  • Next.js / Nuxt / SvelteKit: use the framework's metadata API (generateMetadata, useHead) — never raw tags in components; SSR/SSG pages for anything that must rank (client-only rendering ranks worse and previews break).
  • SPAs: if it must rank, it must be server-rendered or prerendered. Say this plainly when a user wants a client-only marketing site.
  • Social previews render from og tags at share time: absolute URLs for og:image (1200×630), and test with the platform debuggers.

What ships with it: 2 files

7.4 KB alongside SKILL.md

data/

Gives 0 of the 12 instructions most marketing audience skills give in 913 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

  • Apply Poppins font to headingsin 41 of 690, across 6 files
  • Apply Lora font to body textin 41 of 690, across 6 files
  • Use Arial fallback for headingsin 39 of 690, across 4 files
  • Use Georgia fallback for body textin 39 of 690, across 4 files
  • Maintain text hierarchy and formattingin 39 of 690, across 4 files
  • Use accent colors for non-text shapesin 38 of 690, across 3 files
  • Use RGB values for precise color matchingin 38 of 690, across 3 files
  • Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
  • Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
  • Use active voice instead of passive voicein 26 of 690, across 10 files
  • Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
  • Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

  • include the full head block on every page
  • use one h1 per page with descending heading levels
  • treat core web vitals as design constraints
  • ask or infer the target query before building a page
  • run the seo audit before presenting the page
  • use framework metadata apis over raw tags

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.