Skip to content
Merged
Show file tree
Hide file tree
Changes from 18 commits
Commits
Show all changes
86 commits
Select commit Hold shift + click to select a range
b515767
Add GEO + SEO rule for advocacy websites
stuckvgn Mar 28, 2026
6f544d2
Add geo-seo-audit skill for advocacy websites
stuckvgn Mar 28, 2026
3ae21d5
Update skills README to include geo-seo-audit
stuckvgn Mar 28, 2026
d3877f4
Update README file count for geo-seo additions
stuckvgn Mar 28, 2026
73eb0db
Add GEO + SEO instructions to cursor
stuckvgn Mar 28, 2026
fde7b05
Add GEO + SEO instructions to github-copilot
stuckvgn Mar 28, 2026
301c5ef
Add GEO + SEO instructions to windsurf
stuckvgn Mar 28, 2026
c1091f8
Add GEO + SEO instructions to kilo-code
stuckvgn Mar 28, 2026
15bf7d4
Add GEO + SEO instructions to roo-code
stuckvgn Mar 28, 2026
1f8271b
Add GEO + SEO instructions to augment-code
stuckvgn Mar 28, 2026
7cfe374
Add GEO + SEO instructions to github-copilot
stuckvgn Mar 28, 2026
db067c3
Add GEO + SEO instructions to github-copilot
stuckvgn Mar 28, 2026
b1ee8b0
Add GEO + SEO instructions to aider
stuckvgn Mar 28, 2026
c7cd5a9
Add GEO + SEO instructions to gemini-cli
stuckvgn Mar 28, 2026
9d27f05
Add GEO + SEO instructions to jetbrains-junie
stuckvgn Mar 28, 2026
a0c4d35
Add GEO + SEO instructions to agents-md
stuckvgn Mar 28, 2026
99c0622
Expand geo-seo rule with research: Wikipedia/Wikidata, semantic writi…
stuckvgn Mar 28, 2026
afe3f26
Expand geo-seo-audit skill: Wikipedia/Wikidata audit, semantic writin…
stuckvgn Mar 28, 2026
6d70799
Update GEO + SEO content in cursor with research on Wikipedia/Wikidat…
stuckvgn Mar 28, 2026
2f9ffb0
Update GEO + SEO content in cursor with research on Wikipedia/Wikidat…
stuckvgn Mar 28, 2026
f0bd019
Update GEO + SEO content in github-copilot with research on Wikipedia…
stuckvgn Mar 28, 2026
42a3579
Update GEO + SEO content in windsurf with research on Wikipedia/Wikid…
stuckvgn Mar 28, 2026
b0e92a5
Update GEO + SEO content in kilo-code with research on Wikipedia/Wiki…
stuckvgn Mar 28, 2026
10d1c5c
Update GEO + SEO content in roo-code with research on Wikipedia/Wikid…
stuckvgn Mar 28, 2026
b676219
Update GEO + SEO content in augment-code with research on Wikipedia/W…
stuckvgn Mar 28, 2026
58e975b
Update GEO + SEO content in github-copilot with research on Wikipedia…
stuckvgn Mar 28, 2026
a97a7bc
Update GEO + SEO content in aider with research on Wikipedia/Wikidata…
stuckvgn Mar 28, 2026
3e7c658
Update GEO + SEO content in gemini-cli with research on Wikipedia/Wik…
stuckvgn Mar 28, 2026
8a8aa89
Update GEO + SEO content in jetbrains-junie with research on Wikipedi…
stuckvgn Mar 28, 2026
6c77e35
Update GEO + SEO content in agents-md with research on Wikipedia/Wiki…
stuckvgn Mar 28, 2026
ec91941
Expand SEO+GEO rule: CWV 2026 thresholds, E-E-A-T, Helpful Content Sy…
stuckvgn Mar 28, 2026
64fe9e0
Expand skill to 17 steps: CWV updated thresholds, content intent, E-E…
stuckvgn Mar 28, 2026
457194d
Update SEO+GEO content in cursor: CWV 2026 thresholds, E-E-A-T, inten…
stuckvgn Mar 28, 2026
8a24428
Update SEO+GEO content in github-copilot: CWV 2026 thresholds, E-E-A-…
stuckvgn Mar 28, 2026
83fe32a
Update SEO+GEO content in windsurf: CWV 2026 thresholds, E-E-A-T, int…
stuckvgn Mar 28, 2026
e492d4f
Update SEO+GEO content in kilo-code: CWV 2026 thresholds, E-E-A-T, in…
stuckvgn Mar 28, 2026
3d59d39
Update SEO+GEO content in roo-code: CWV 2026 thresholds, E-E-A-T, int…
stuckvgn Mar 28, 2026
5b5570e
Update SEO+GEO content in augment-code: CWV 2026 thresholds, E-E-A-T,…
stuckvgn Mar 28, 2026
aa9c921
Update SEO+GEO content in github-copilot: CWV 2026 thresholds, E-E-A-…
stuckvgn Mar 28, 2026
ca74cf8
Update SEO+GEO content in aider: CWV 2026 thresholds, E-E-A-T, intent…
stuckvgn Mar 28, 2026
bf8ba03
Update SEO+GEO content in gemini-cli: CWV 2026 thresholds, E-E-A-T, i…
stuckvgn Mar 28, 2026
a5d5edf
Update SEO+GEO content in jetbrains-junie: CWV 2026 thresholds, E-E-A…
stuckvgn Mar 28, 2026
0d10f52
Update SEO+GEO content in agents-md: CWV 2026 thresholds, E-E-A-T, in…
stuckvgn Mar 28, 2026
d02038f
Fix MD022: add blank line after When to Use heading
stuckvgn Mar 28, 2026
04a691a
Expand copilot prompt: add Wikipedia/Wikidata step, defensive review …
stuckvgn Mar 28, 2026
df5f862
Condense GEO+SEO section in GEMINI.md to reduce instruction budget (G…
stuckvgn Mar 28, 2026
2ca9341
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
98340e0
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
b49b2a4
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
476841f
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
08a2b02
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
798a980
feat(geo-seo): fix LCP threshold to 2.5s in copilot prompt
stuckvgn Mar 28, 2026
4055488
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
b5397c3
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
cca8793
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
397e645
feat(geo-seo): add CRO, analytics, i18n sections; fix LCP threshold t…
stuckvgn Mar 28, 2026
4d08277
feat(geo-seo): update single-file tools with CRO, analytics, i18n; fi…
stuckvgn Mar 28, 2026
c66e2d6
feat(geo-seo): update single-file tools with CRO, analytics, i18n; fi…
stuckvgn Mar 28, 2026
e4b8fe9
feat(geo-seo): update single-file tools with CRO, analytics, i18n; fi…
stuckvgn Mar 28, 2026
b726ccf
feat(geo-seo): update single-file tools with CRO, analytics, i18n; fi…
stuckvgn Mar 28, 2026
e7f8a74
fix: add blank line between HTML comment and heading in windsurf rule…
stuckvgn Mar 28, 2026
3acfe94
fix: correct malformed HTML comment in windsurf rule file
stuckvgn Mar 28, 2026
7b19975
Fix CodeRabbit comments in windsurf geo-seo rules
stuckvgn Mar 29, 2026
f3b433b
Fix phrasing: 'position drops of 0.8 places' → 'average ranking drop …
stuckvgn Mar 29, 2026
4c1b6be
Fix CodeRabbit full review findings
stuckvgn Mar 29, 2026
715973c
Fix remaining CodeRabbit comments
stuckvgn Mar 29, 2026
fd10bfc
Apply consistent geo-seo fixes across all 8 remaining tool files
stuckvgn Mar 29, 2026
90e6312
Fix step numbering in SKILL.md files: 17 numbered steps + unnumbered …
stuckvgn Mar 29, 2026
2ecfef9
Fix: append SKILL.md canonical reference to geo-seo-audit README entry
stuckvgn Mar 29, 2026
8b6933f
Fix 3 more CodeRabbit issues
stuckvgn Mar 29, 2026
b5cc0a6
Fix schema.org validator URLs and README copilot skill count
stuckvgn Mar 29, 2026
5de9b40
Fix 4 CodeRabbit comments: file counts, COI guardrails, glob patterns…
stuckvgn Mar 29, 2026
08f09e4
Add Wikipedia COI guardrails across all 12 tool files + citation sources
stuckvgn Mar 29, 2026
0f9d1c5
Fix prompt step mapping: remove Step 15 from omitted list (Step 9 cov…
stuckvgn Mar 29, 2026
9e938b5
Fix schema.org validator URLs and add cursor frontmatter sync fields
stuckvgn Mar 29, 2026
901c8c1
Fix crawler lists, tighten applyTo glob, add COI/training-block/Unico…
stuckvgn Mar 29, 2026
3073a2c
Add source citations to quantitative claims; fix cursor source frontm…
stuckvgn Mar 29, 2026
eeab5b2
Add Permissions-Policy and COOP to security headers in canonical rule…
stuckvgn Mar 29, 2026
9340bef
Add Permissions-Policy and COOP to cursor rules security headers
stuckvgn Mar 29, 2026
0b5238e
Add frontmatter to augment/roo rules; add Perm-Policy+COOP to augment…
stuckvgn Mar 29, 2026
cc6f9e4
Add source citations to all remaining geo-seo files; fix CSS logical …
stuckvgn Mar 29, 2026
e6f6b11
Add frontmatter and Permissions-Policy+COOP headers to kilo-code and …
stuckvgn Mar 29, 2026
fa74b6e
Fix CodeRabbit feedback: autocomplete attr, utility class wording, se…
stuckvgn Mar 31, 2026
10510d9
Fix README process skills count: add missing geo-seo-audit entry to list
stuckvgn Mar 31, 2026
f481a4b
Add geo-seo-audit skill to kilo-code; update skill counts to 7 in README
stuckvgn Mar 31, 2026
3dcc08d
Update kilo-code skills index; fix repetitive 'Is' phrasing in geo-se…
stuckvgn Mar 31, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ cp agents-md/AGENTS.md your-project/

| Tool | Directory | Files | Format Notes |
|------|-----------|------:|--------------|
| Claude Code | `claude-code/` | 15 | CLAUDE.md + 7 scoped rules + 6 skills + hooks template |
| Claude Code | `claude-code/` | 17 | CLAUDE.md + 8 scoped rules + 7 skills + hooks template |
| Cursor | `cursor/` | 14 | .cursorrules + 13 .mdc files with 4 activation modes |
| GitHub Copilot | `github-copilot/` | 22 | copilot-instructions.md + 7 instructions + 6 prompts + 2 chat modes + 6 skills |
| Windsurf | `windsurf/` | 14 | 14 .md files in .windsurf/rules/ with 4 trigger types, within 6K/12K char limits |
Expand Down
18 changes: 18 additions & 0 deletions agents-md/AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -486,3 +486,21 @@ desloppify next
Do not be lazy. Large refactors and small detailed fixes — do both with equal energy. No task is too big or too small. Fix things properly, not minimally.

Use `plan` / `plan queue` to reorder priorities or cluster related issues. Rescan periodically. The scan output includes agent instructions — follow them, do not substitute your own analysis.

## GEO + SEO — Advocacy Website Visibility

Websites built for animal advocacy serve two discovery channels: traditional search engines and AI answer systems (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Bing Copilot). Approximately 60% of searches end without a click — AI systems are the fastest-growing discovery channel with distinct citation requirements. Apply these rules when building or modifying any public-facing advocacy website.

**HTML structure.** Every page needs exactly one `<h1>` containing the primary topic. Use a logical heading hierarchy (h1 > h2 > h3), never skipping levels. Phrase h2 headings as questions — question-based headings produce 7× more AI citations for smaller sites. The first paragraph after any heading must directly answer that question in 40-60 words; AI systems pull from the first 30% of content 44% of the time. Keep paragraphs to 2-4 sentences (40-60 words). Structure content as self-contained 120-180 word modules — this modular pattern generates 70% more ChatGPT citations than unstructured prose. Use semantic HTML correctly: article, section, nav, aside, header, footer, main. Add lang attribute to html element. Every img must have descriptive alt text. Every anchor must have meaningful text — never "click here". Use table for comparison data (32.5% of AI-cited content uses tables), ol and ul for lists (78% of AI answers include list formats), blockquote with cite attribute for expert quotations (+28-40% AI visibility). Flag any content rendered exclusively by JavaScript — AI crawlers often skip JS rendering. Do NOT keyword-stuff — stuffing decreases AI visibility by 10%.

**Structured data (JSON-LD).** This is the single highest-leverage GEO action: 41% citation rate with schema vs 15% without, yet only 12.4% of websites implement it. Every page needs Organization + WebSite schema in a @graph array. Every content page needs Article schema with headline, author (with name, url, jobTitle), publisher, datePublished, dateModified, image, and description. Any page with Q&A content needs FAQPage schema with 40-80 word direct answers per question. Also implement when applicable: HowTo, BreadcrumbList, SoftwareApplication, Event, Dataset, Person. Always use JSON-LD format, not Microdata. Keep dateModified accurate. Validate at schema.org/validator.

**Meta tags.** Title tag: Primary Keyword — Brand Name, 50-60 chars, keywords first, unique per page. Meta description: 150-160 chars, direct factual answer to the primary query, one specific statistic, never duplicated across pages. Every page needs a canonical link tag, full Open Graph tags (og:title, og:description, og:type, og:url, og:image, og:site_name), Twitter Card tags, and article timestamp tags in ISO 8601 format.

**robots.txt.** Allow AI citation crawlers — they power AI answer systems: OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Claude-SearchBot, Applebot, Amazonbot. Optionally block AI training crawlers if not consenting to training use: GPTBot, CCBot, Google-Extended. Include a Sitemap directive. Note: blocking Googlebot blocks both Google Search AND Google AI Overviews — there is no way to separate them.

**Sitemap and architecture.** XML sitemap at /sitemap.xml with accurate lastmod dates — never fake them. Submit to Google Search Console and Bing Webmaster Tools. Regenerate automatically on content changes. Use descriptive hyphenated lowercase URLs under 75 characters, max 3 levels deep, canonical tags on every page. Implement hub-and-spoke topic cluster model: pillar page (2,000-4,000 words) + 8-15 cluster pages with bidirectional links — increases AI citation rate from 12% to 41%. Display "Last Updated" visibly with time[datetime] tag; synchronize with dateModified in schema (76% of most-cited AI content was updated within 30 days).

**Performance.** AI crawlers timeout at 1-5 seconds: TTFB under 200ms, LCP under 2.5s, CLS under 0.1, page weight under 1MB. Require SSR or SSG — AI crawlers often skip JavaScript rendering. Enforce HTTPS.

**Content patterns that earn AI citations.** Citable paragraph: direct statement of fact, specific statistic with attribution, brief elaboration, named source and date. Author attribution on every content page — visible name, credentials, link to profile page with Person schema — increases AI citations by 40%. Pages over 2,900 words are 59% more likely to be cited. Original or proprietary data generates 4.31× more citations per URL. Adding statistics to claims increases AI visibility by 41%. Citing credible sources inline increases AI visibility by 30-40%. Expert quotations increase AI visibility by 28-40%.
18 changes: 18 additions & 0 deletions aider/CONVENTIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -344,3 +344,21 @@ desloppify next
**The loop:** run `next`. It tells you what to fix now, which file, and the resolve command to run when done. Fix it, resolve it, run `next` again. This is your main job. Use `desloppify backlog` only to inspect broader open work not currently driving execution.

Large refactors and small detailed fixes — do both with equal energy. Fix things properly, not minimally. Use `plan` / `plan queue` to reorder priorities or cluster related issues. Rescan periodically. The scan output includes agent instructions — follow them, do not substitute your own analysis.

## GEO + SEO — Advocacy Website Visibility

Websites built for animal advocacy serve two discovery channels: traditional search engines and AI answer systems (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Bing Copilot). Approximately 60% of searches end without a click — AI systems are the fastest-growing discovery channel with distinct citation requirements. Apply these rules when building or modifying any public-facing advocacy website.

**HTML structure.** Every page needs exactly one `<h1>` containing the primary topic. Use a logical heading hierarchy (h1 > h2 > h3), never skipping levels. Phrase h2 headings as questions — question-based headings produce 7× more AI citations for smaller sites. The first paragraph after any heading must directly answer that question in 40-60 words; AI systems pull from the first 30% of content 44% of the time. Keep paragraphs to 2-4 sentences (40-60 words). Structure content as self-contained 120-180 word modules — this modular pattern generates 70% more ChatGPT citations than unstructured prose. Use semantic HTML correctly: article, section, nav, aside, header, footer, main. Add lang attribute to html element. Every img must have descriptive alt text. Every anchor must have meaningful text — never "click here". Use table for comparison data (32.5% of AI-cited content uses tables), ol and ul for lists (78% of AI answers include list formats), blockquote with cite attribute for expert quotations (+28-40% AI visibility). Flag any content rendered exclusively by JavaScript — AI crawlers often skip JS rendering. Do NOT keyword-stuff — stuffing decreases AI visibility by 10%.

Comment on lines +426 to +429
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

What are the native CSS logical properties corresponding to ps-4, pe-4, and text-start, and are those names native CSS properties or utility framework classes?

💡 Result:

The classes ps-4, pe-4, and text-start are utility framework classes from Tailwind CSS, not native CSS properties. Their corresponding native CSS logical properties are: - ps-4 → padding-inline-start: 1rem (16px) - pe-4 → padding-inline-end: 1rem (16px) - text-start → text-align: start

Citations:


Clarify that those are utility framework classes, not native CSS logical properties.

The text presents ps-4, pe-4, and text-start as CSS logical properties, but these are Tailwind utility classes. Using native CSS property names prevents confusion for teams using plain CSS.

Suggested fix
-CSS logical properties (`ps-4`, `pe-4`, `text-start`) handle RTL layout automatically.
+Use native CSS logical properties (`padding-inline-start`, `padding-inline-end`, `text-align: start`) for RTL layout. If using a utility framework, use its equivalents (for example: `ps-4`, `pe-4`, `text-start`).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@aider/CONVENTIONS.md` around lines 426 - 429, Update the Internationalization
section to clarify that ps-4, pe-4, and text-start are Tailwind (or other
utility framework) classes rather than native CSS logical properties; change the
wording to recommend using CSS logical properties (e.g., padding-inline-start,
padding-inline-end, text-align: start) for plain-CSS projects and note that
utility classes like ps-4/pe-4/text-start provide the equivalent behavior in
Tailwind/Bootstrap-style frameworks so teams understand the distinction.

**Structured data (JSON-LD).** This is the single highest-leverage GEO action: 41% citation rate with schema vs 15% without, yet only 12.4% of websites implement it. Every page needs Organization + WebSite schema in a @graph array. Every content page needs Article schema with headline, author (with name, url, jobTitle), publisher, datePublished, dateModified, image, and description. Any page with Q&A content needs FAQPage schema with 40-80 word direct answers per question. Also implement when applicable: HowTo, BreadcrumbList, SoftwareApplication, Event, Dataset, Person. Always use JSON-LD format, not Microdata. Keep dateModified accurate. Validate at schema.org/validator.

**Meta tags.** Title tag: Primary Keyword — Brand Name, 50-60 chars, keywords first, unique per page. Meta description: 150-160 chars, direct factual answer to the primary query, one specific statistic, never duplicated across pages. Every page needs a canonical link tag, full Open Graph tags (og:title, og:description, og:type, og:url, og:image, og:site_name), Twitter Card tags, and article timestamp tags in ISO 8601 format.

**robots.txt.** Allow AI citation crawlers — they power AI answer systems: OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Claude-SearchBot, Applebot, Amazonbot. Optionally block AI training crawlers if not consenting to training use: GPTBot, CCBot, Google-Extended. Include a Sitemap directive. Note: blocking Googlebot blocks both Google Search AND Google AI Overviews — there is no way to separate them.

**Sitemap and architecture.** XML sitemap at /sitemap.xml with accurate lastmod dates — never fake them. Submit to Google Search Console and Bing Webmaster Tools. Regenerate automatically on content changes. Use descriptive hyphenated lowercase URLs under 75 characters, max 3 levels deep, canonical tags on every page. Implement hub-and-spoke topic cluster model: pillar page (2,000-4,000 words) + 8-15 cluster pages with bidirectional links — increases AI citation rate from 12% to 41%. Display "Last Updated" visibly with time[datetime] tag; synchronize with dateModified in schema (76% of most-cited AI content was updated within 30 days).

**Performance.** AI crawlers timeout at 1-5 seconds: TTFB under 200ms, LCP under 2.5s, CLS under 0.1, page weight under 1MB. Require SSR or SSG — AI crawlers often skip JavaScript rendering. Enforce HTTPS.

**Content patterns that earn AI citations.** Citable paragraph: direct statement of fact, specific statistic with attribution, brief elaboration, named source and date. Author attribution on every content page — visible name, credentials, link to profile page with Person schema — increases AI citations by 40%. Pages over 2,900 words are 59% more likely to be cited. Original or proprietary data generates 4.31× more citations per URL. Adding statistics to claims increases AI visibility by 41%. Citing credible sources inline increases AI visibility by 30-40%. Expert quotations increase AI visibility by 28-40%.
Loading
Loading