Add SEO & GEO Optimizer to Utilities#178
Add SEO & GEO Optimizer to Utilities#178Aryanpanwar10005 wants to merge 1 commit intoPatrickJS:mainfrom
Conversation
📝 WalkthroughWalkthroughThe PR introduces a comprehensive SEO & GEO Optimizer tool by adding a new utilities section entry to the root README, establishing a new directory with an extensive workflow configuration file, and providing accompanying documentation for the tool's features and usage. Changes
Estimated Code Review Effort🎯 3 (Moderate) | ⏱️ ~25 minutes Suggested Reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Line 17: Remove the accidental blank lines introduced immediately after the
"## Sponsorships" headings; locate both occurrences of the header (the "##
Sponsorships" lines) and delete the extra empty line following each so the
heading is directly followed by the next content paragraph, restoring the
original spacing and minimizing the diff noise.
In `@rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules`:
- Line 302: Update the unsubstantiated "3.2×" claim in the T3-1 rule text
("Pages with FAQPage schema are 3.2× more likely to appear in Google AI
Overviews") by either adding a verifiable official source URL that supports that
exact statistic (per LAW 6) or replacing the hard numeric claim with a softened,
source-free phrasing (e.g., "more likely" or "can improve chances") and include
the required citation for the FAQPage guidance (Google Developers FAQPage
structured data page) when available; apply the same change to the duplicate
occurrence of the sentence elsewhere in the file.
- Line 205: Replace the deprecated "Mobile-Friendly Test" markdown link entries
(the table cell containing "Mobile experience | Does the mobile version work
cleanly? | [Mobile-Friendly
Test](https://search.google.com/test/mobile-friendly)") at the four occurrences
(previously at lines 205, 291, 637, 775) with current alternatives such as a
Lighthouse link (note Lighthouse is in Chrome DevTools), PageSpeed Insights, or
Google Search Console's Mobile Usability report; update the bracketed link text
and URL accordingly (e.g., replace "[Mobile-Friendly
Test](https://search.google.com/test/mobile-friendly)" with "[PageSpeed
Insights](https://developers.google.com/speed/pagespeed/insights/)" or another
chosen alternative) so each table row points to a supported, current
mobile-testing resource.
- Around line 7-11: Update the "Verified against:" block so the living-document
citation is explicit: replace or annotate the "Google Search Central — December
2025" entry to indicate whether it refers to a snapshot taken on that date or to
the current, continuously-updated Search Central guidance, and make its format
consistent with other living-doc citations like "Bing Webmaster Guidelines";
edit the "Verified against:" list entry (the line containing "Google Search
Central — December 2025") to either add "(snapshot: YYYY-MM-DD)" or change to
"Google Search Central (current guidance)" as appropriate.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
README.mdrules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrulesrules/seo-geo-optimizer-cursorrules-prompt-file/README.md
| [Cursor AI](https://cursor.sh/) is an AI-powered code editor. `.cursorrules` files define custom rules for Cursor AI to follow when generating code, allowing you to tailor its behavior to your specific needs and preferences. | ||
|
|
||
| ## Sponsorships | ||
|
|
There was a problem hiding this comment.
Spurious blank-line additions in the Sponsorships sections.
Lines 17 and 330 introduce extra blank lines after the ## Sponsorships headings. These appear to be unintentional whitespace changes unrelated to the PR's purpose. Consider reverting these to keep the diff minimal and avoid formatting noise.
Also applies to: 330-330
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` at line 17, Remove the accidental blank lines introduced
immediately after the "## Sponsorships" headings; locate both occurrences of the
header (the "## Sponsorships" lines) and delete the extra empty line following
each so the heading is directly followed by the next content paragraph,
restoring the original spacing and minimizing the diff noise.
| **Verified against:** | ||
| - Google Search Central — December 2025 | ||
| - Bing Webmaster Guidelines — 2025 | ||
| - Google June 2025 Core Update | ||
| - Core Web Vitals spec — March 2024 (INP replaces FID — all FID references are outdated) |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Google June 2025 core update
💡 Result:
Google’s June 2025 core update was a broad (“regular”) update to Google Search’s core ranking systems.
- Rollout window: June 30, 2025 → July 17, 2025 (about 16 days, 18 hours). [1][2]
- Where confirmed: Google listed it under Ranking incidents on the Google Search Status Dashboard. [1]
- What to do: Now that rollout is finished, review performance changes starting June 30, 2025, compare pre-/post-update trends, and focus on improving overall content quality rather than trying to “fix” a specific penalty (core updates aren’t targeted penalties). [2][3]
Sources: [1] Google Search Status Dashboard, [2] Search Engine Land, [3] Search Engine Journal.
🌐 Web query:
Core Web Vitals INP FID replacement 2024 2025
💡 Result:
- What replaced FID? Interaction to Next Paint (INP) replaced First Input Delay (FID) as the Core Web Vitals responsiveness metric. [1][2]
- When did the change happen? March 12, 2024—INP became an official Core Web Vital and FID stopped being a Core Web Vital. [1][2]
- Tooling / reporting impact: Google’s tooling switched CWV pass/fail evaluation to INP instead of FID, and Chrome UX Report notes this is when INP replaced FID (with FID considered deprecated and later removed from Chrome tooling). [3]
- INP thresholds (field data, 75th percentile):
- Good: ≤ 200 ms
- Needs improvement: 200–500 ms
- Poor: > 500 ms [4]
Bottom line for 2024–2025: If you’re optimizing “Core Web Vitals” after March 12, 2024, you should optimize and report INP (not FID) for responsiveness. [1][2][3]
Sources
[1] https://web.dev/blog/inp-cwv-march-12
[2] https://developers.google.com/search/blog/2023/05/introducing-inp
[3] https://developer.chrome.com/docs/crux/release-notes
[4] https://web.dev/inp/
🌐 Web query:
Google Search Central documentation
💡 Result:
Google Search Central documentation (Google for Developers) is here:
https://developers.google.com/search/docs
[1]
Key starting points inside the docs:
- Google Search Essentials (technical requirements, spam policies, key best practices) [2]
- SEO Starter Guide (intro best practices for crawl/index/understand) [3]
- Crawling & indexing docs (robots.txt, sitemaps, URL structure, crawl management) [4]
- Creating helpful, reliable, people-first content (quality self-assessment guidance) [5]
To track major doc changes, Google also maintains a “Latest documentation updates” page (with an RSS feed). [6]
🌐 Web query:
Bing Webmaster Guidelines 2025
💡 Result:
Web search failed: Server error: no LLM provider could handle the message
🌐 Web query:
Bing Webmaster Tools guidelines documentation
💡 Result:
- Bing Webmaster Guidelines (official) — Bing’s rules on acceptable vs. manipulative behavior and what can lead to ranking/indexing actions. (bing.com)
- Bing Webmaster Tools Help / Documentation hub (official) — Central help center for Bing Webmaster Tools features and how-to docs (includes access to guidelines). (support.microsoft.com)
- Bing Webmaster API documentation (official, Microsoft Learn) — Overview of the Bing Webmaster API, capabilities, and documentation structure. (learn.microsoft.com)
- Bing Webmaster API: Getting started (official, Microsoft Learn) — Practical setup/usage guidance (e.g., SOAP endpoint/WSDL and sample workflow). (learn.microsoft.com)
- Bing Webmaster API: OAuth 2.0 (official, Microsoft Learn) — OAuth scopes and authorization details for API access. (learn.microsoft.com)
- Bing Webmaster Tools blog (official) — Product updates and guidance (useful for changes/new features). (blogs.bing.com)
Citations:
- 1: https://www.bing.com/webmasters/help/webmasters-guidelines-3462597?utm_source=openai
- 2: https://support.microsoft.com/en-us/topic/help-with-bing-webmaster-tools-03681ed9-89f8-4616-9841-36e299185279?utm_source=openai
- 3: https://learn.microsoft.com/bingwebmaster/?utm_source=openai
- 4: https://learn.microsoft.com/en-us/bingwebmaster/getting-started?utm_source=openai
- 5: https://learn.microsoft.com/en-us/bingwebmaster/oauth2?utm_source=openai
- 6: https://blogs.bing.com/webmaster/June-2025/Start-Using-Bing-Webmaster-Tools-to-Improve-Your-Site-Visibility?utm_source=openai
Clarify citation style for continuously-updated resources.
The "Google June 2025 Core Update," "Bing Webmaster Guidelines," and "Core Web Vitals spec — March 2024 (INP replaces FID)" are all verifiable and accurate. However, citing "Google Search Central — December 2025" is misleading: Google Search Central (developers.google.com/search/docs) is a continuously-updated living documentation, not a versioned release dated to a specific month. Consider clarifying whether you mean a snapshot from December 2025 or just the current Search Central guidance. Either way, the reference practice should align with how you cite other living documents (e.g., Bing Webmaster Guidelines, which are also continuously maintained).
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules` around lines 7
- 11, Update the "Verified against:" block so the living-document citation is
explicit: replace or annotate the "Google Search Central — December 2025" entry
to indicate whether it refers to a snapshot taken on that date or to the
current, continuously-updated Search Central guidance, and make its format
consistent with other living-doc citations like "Bing Webmaster Guidelines";
edit the "Verified against:" list entry (the line containing "Google Search
Central — December 2025") to either add "(snapshot: YYYY-MM-DD)" or change to
"Google Search Central (current guidance)" as appropriate.
| | 10 | Content freshness | When were key pages last updated? | Google cache check: `cache:url` | | ||
| | 11 | Keyword gap | Keywords they rank for that user doesn't | SEMrush Keyword Gap (free trial) | | ||
| | 12 | Featured snippets / AI Overviews | Do they own any for target keywords? | Manual search | | ||
| | 13 | Mobile experience | Does the mobile version work cleanly? | [Mobile-Friendly Test](https://search.google.com/test/mobile-friendly) | |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check if the file exists and examine the specified lines
find . -name ".cursorrules" -o -name "*cursorrules*" | head -20Repository: PatrickJS/awesome-cursorrules
Length of output: 1204
🏁 Script executed:
# Try to locate the specific file mentioned
fd ".cursorrules" --type fRepository: PatrickJS/awesome-cursorrules
Length of output: 133
🌐 Web query:
Google Mobile-Friendly Test tool deprecated 2023 retirement
💡 Result:
Google announced in April 2023 that it would retire (sunset) Search Console’s Mobile Usability report, the Mobile-Friendly Test tool, and the Mobile-Friendly Test API, with the retirement taking effect on December 1, 2023. [1]
Google’s own Search Central documentation was later updated to confirm the tools were retired as of December 2023 / December 1, 2023. [2][3]
After retirement: the Mobile-Friendly Test experience was redirected toward Lighthouse / Chrome Lighthouse as an alternative. [1]
Sources: [1] [2] [3]
🏁 Script executed:
# Find the seo-geo-optimizer file
find . -path "*seo-geo-optimizer*" -name ".cursorrules" -type fRepository: PatrickJS/awesome-cursorrules
Length of output: 135
🏁 Script executed:
# Check the file and examine the specific lines mentioned
if [ -f "rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules" ]; then
echo "=== Line 205 ==="; sed -n '205p' "rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules"
echo "=== Line 291 ==="; sed -n '291p' "rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules"
echo "=== Line 637 ==="; sed -n '637p' "rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules"
echo "=== Lines 775-776 ==="; sed -n '775,776p' "rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules"
fiRepository: PatrickJS/awesome-cursorrules
Length of output: 698
🏁 Script executed:
# Also check for the URL pattern across the file to see all occurrences
rg "search.google.com/test/mobile-friendly" "rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules" -nRepository: PatrickJS/awesome-cursorrules
Length of output: 596
Update deprecated Google Mobile-Friendly Test references to current alternatives.
Google retired the Mobile-Friendly Test tool on December 1, 2023. Replace the four references at lines 205, 291, 637, and 775 with current alternatives: Lighthouse (built into Chrome DevTools), PageSpeed Insights, or the Mobile Usability report in Google Search Console.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules` at line 205,
Replace the deprecated "Mobile-Friendly Test" markdown link entries (the table
cell containing "Mobile experience | Does the mobile version work cleanly? |
[Mobile-Friendly Test](https://search.google.com/test/mobile-friendly)") at the
four occurrences (previously at lines 205, 291, 637, 775) with current
alternatives such as a Lighthouse link (note Lighthouse is in Chrome DevTools),
PageSpeed Insights, or Google Search Console's Mobile Usability report; update
the bracketed link text and URL accordingly (e.g., replace "[Mobile-Friendly
Test](https://search.google.com/test/mobile-friendly)" with "[PageSpeed
Insights](https://developers.google.com/speed/pagespeed/insights/)" or another
chosen alternative) so each table row points to a supported, current
mobile-testing resource.
|
|
||
| | ID | Action | Why | Official Reference | | ||
| |----|--------|-----|--------------------| | ||
| | T3-1 | Add `FAQPage` JSON-LD schema on all key pages with real user questions | **Pages with FAQPage schema are 3.2× more likely to appear in Google AI Overviews** | [Google: FAQPage](https://developers.google.com/search/docs/appearance/structured-data/faqpage) | |
There was a problem hiding this comment.
Unsubstantiated "3.2×" statistic claim.
Lines 302 and 393 state: "Pages with FAQPage schema are 3.2× more likely to appear in Google AI Overviews." This specific statistic lacks an official citation. LAW 6 of this very skill file states "Every SEO or GEO recommendation must include the official source URL. No recommendation without a citation." The claim should either be cited with a verifiable source or softened to avoid misleading users.
Also applies to: 393-393
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@rules/seo-geo-optimizer-cursorrules-prompt-file/.cursorrules` at line 302,
Update the unsubstantiated "3.2×" claim in the T3-1 rule text ("Pages with
FAQPage schema are 3.2× more likely to appear in Google AI Overviews") by either
adding a verifiable official source URL that supports that exact statistic (per
LAW 6) or replacing the hard numeric claim with a softened, source-free phrasing
(e.g., "more likely" or "can improve chances") and include the required citation
for the FAQPage guidance (Google Developers FAQPage structured data page) when
available; apply the same change to the duplicate occurrence of the sentence
elsewhere in the file.
1 participant
Adding SEO & GEO Optimizer, a universal AI skill for Technical SEO, Content Strategy, Schema Markup, Core Web Vitals, and Generative Engine Optimization (GEO). Compatible with Cursor, Windsurf, Lovable, Bolt, and more.
Summary by CodeRabbit
New Features
Documentation