seo-google-rules

A set of Google-focused SEO instructions for a Next.js website. SEO, or search engine optimization, is the practice of making pages easier for search engines to find, understand, and list.

In plain words
What is it for?
Use it when building or reviewing public Next.js pages, especially business sites, to guide semantic HTML, headings, metadata, image text, and server-rendered or prebuilt content.
Why use it?
It gives developers a checklist for common technical SEO requirements, reducing missed settings such as sitemaps, robots.txt, canonical URLs, and accessible page structure.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/jondoescoding/jondoescoding-coding-rules/seo-google-rules
Clone the repo
git clone --depth 1 https://github.com/jondoescoding/jondoescoding-coding-rules
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,162 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.05162
Opus 5 $0.00009 $0.02581
Sonnet 5 $0.00003 $0.01032
Haiku 4.5 $0.00002 $0.00516

Measured yesterday against content hash de99f68004b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

seo-google-rules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/cursor-rules/seo/seo-google-rules.mdc · 770 lines

How it starts

The opening of the file, as written. The whole thing — 770 lines — stays where its author put it; the contents beside it link to each section on GitHub.

13. Monitoring & Testing

SEO Checklist for Every Page
  • Unique title tag (50-60 characters)
  • Meta description (150-160 characters)
  • One H1 tag with target keyword
  • Proper heading hierarchy (H1 → H2 → H3)
  • Alt text for all images
  • [ ]# SEO-Optimized Cursor Rules for Next.js Business Website

Project Context

You are developing a SEO-optimized business website using Next.js 15+, React 19, Tailwind CSS, and MongoDB. Follow Google's SEO Starter Guide principles strictly. Prioritize technical SEO and mobile-first development. This project uses the App Router architecture.

Core SEO Principles

1. Technical SEO Foundation

  • Always use semantic HTML5 elements (<header>, <nav>, <main>, <article>, <section>, <aside>, <footer>)
  • Implement proper heading hierarchy - Only one <h1> per page, followed by <h2>, <h3> in logical order
  • Generate XML sitemaps automatically using next-sitemap package
  • Create robots.txt with proper directives
  • Implement canonical URLs to prevent duplicate content issues
  • Use Server-Side Rendering (SSR) or Static Site Generation (SSG) for all public pages

2. Next.js SEO Implementation

Metadata API Usage (Next.js 15)
// Always use Next.js 15 Metadata API for SEO
import type { Metadata } from 'next';

export const metadata: Metadata = {
  title: 'Page Title - Business Name',
  description: 'Compelling description under 160 characters that includes target keywords naturally',
  keywords: ['relevant', 'keywords', 'for', 'SEO'],
  authors: [{ name: 'Author Name' }],
  creator: 'Business Name',
  publisher: 'Business Name',
  formatDetection: {
    email: false,
    address: false,
    telephone: false,
  },
  metadataBase: new URL('https://yourdomain.com'),
  openGraph: {
    title: 'Page Title - Business Name',
    description: 'Compelling description for social sharing',
    url: 'https://yourdomain.com/current-page',
    siteName: 'Business Name',
    images: [
      {
        url: '/og-image.jpg',
        width: 1200,
        height: 630,
        alt: 'Descriptive alt text for OG image',
      }
    ],
    locale: 'en_US',
    type: 'website',
  },
  twitter: {
    card: 'summary_large_image',
    title: 'Page Title - Business Name',
    description: 'Compelling description for Twitter',
    creator: '@yourtwitterhandle',
    images: ['/twitter-image.jpg'],
  },
  alternates: {
    canonical: 'https://yourdomain.com/current-page',
    languages: {
      'en-US': 'https://yourdomain.com/en-US',
      'es-ES': 'https://yourdomain.com/es-ES',
    },
  },
  robots: {
    index: true,
    follow: true,
    nocache: true,
    googleBot: {
      index: true,
      follow: true,
      'max-video-preview': -1,
      'max-image-preview': 'large',
      'max-snippet': -1,
    },
  },
  verification: {
    google: 'google-site-verification-code',
    yandex: 'yandex-verification-code',
    yahoo: 'yahoo-verification-code',
  },
};

Read the full file on GitHub · 770 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 770 lines · 17 tokens per session scan A de99f68004b2

Subscribe to this mod's changes

seo-google-rules is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 5,162 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.