fennecseo-audit
starsforks
How to install fennecseo-audit?
berabuddies/semia/fennecseo-audit
$npx -y skills add berabuddies/Semia --skill fennecseo-auditUses Fennec SEO Auditor results to audit a URL. Invoke when user wants a quick on‑page/technical SEO health check or to verify favicon/meta/schema and GEO readiness.
SKILL.md
| 1 | # Fennec SEO Audit Skill (with Fennec SEO Auditor Extension) |
| 2 | |
| 3 | This Skill is designed to work together with the Chrome extension **Fennec SEO Auditor** to run a quick SEO health check on any given page. |
| 4 | |
| 5 | Typical use cases: |
| 6 | |
| 7 | - Get a fast overview of a page’s SEO basics (title, meta, headings, canonicals, etc.) |
| 8 | - Verify favicon, Open Graph and structured data exposure |
| 9 | - Spot common technical issues (HTTP status code, redirects, indexability, robots rules) |
| 10 | - Judge whether a page is “GEO‑ready” as a candidate source for RAG / LLM answers |
| 11 | |
| 12 | > Chrome extension link: |
| 13 | > https://chromewebstore.google.com/detail/fennec-seo-auditor/fifppiokpmlgceojhfdjbjjapbephcdo |
| 14 | |
| 15 | --- |
| 16 | |
| 17 | ## When to invoke this Skill |
| 18 | |
| 19 | Use `fennec-seo-audit-en` when: |
| 20 | |
| 21 | - The user provides a URL and asks for a **quick SEO audit / health check** |
| 22 | - The user wants to confirm favicon / meta / Open Graph / structured data are implemented correctly |
| 23 | - A new article / landing page has just been published and needs a basic SEO / GEO review |
| 24 | - The user wants to use a real page as a **GEO example**, to see how well it exposes: |
| 25 | - indexability signals |
| 26 | - semantic structure |
| 27 | - brand / entity signals |
| 28 | |
| 29 | Avoid using this Skill as: |
| 30 | |
| 31 | - A full‑site crawler or large‑scale technical audit (it’s better suited for spot checks) |
| 32 | - A replacement for log analysis or server‑level diagnostics |
| 33 | |
| 34 | --- |
| 35 | |
| 36 | ## Human steps (what the user does with the browser) |
| 37 | |
| 38 | 1. Install and enable the **Fennec SEO Auditor** Chrome extension |
| 39 | Link: `https://chromewebstore.google.com/detail/fennec-seo-auditor/fifppiokpmlgceojhfdjbjjapbephcdo` |
| 40 | |
| 41 | 2. Open the target page you want to audit |
| 42 | (e.g. a blog post, product detail page, homepage, documentation page) |
| 43 | |
| 44 | 3. Click the **Fennec SEO Auditor** icon in the browser toolbar: |
| 45 | - Run the standard audit (On‑page / HTML / Links / Images, etc.) |
| 46 | - Wait for the extension to finish and show the report |
| 47 | |
| 48 | 4. Share the key parts of the report with the assistant: |
| 49 | - Either copy key findings as text |
| 50 | - Or summarize / extract the main issues |
| 51 | - Screenshots are fine too if the platform supports them |
| 52 | |
| 53 | The assistant will then interpret the audit and turn it into a clear action plan. |
| 54 | |
| 55 | --- |
| 56 | |
| 57 | ## Assistant responsibilities when this Skill is invoked |
| 58 | |
| 59 | When `fennec-seo-audit-en` is triggered, the assistant should: |
| 60 | |
| 61 | 1. Make sure the user has run Fennec SEO Auditor on the target URL (and guide them if not). |
| 62 | |
| 63 | 2. Parse and structure the audit output, covering at least: |
| 64 | - **Page basics**: URL, title, meta description, H1/H2, main intent |
| 65 | - **Technical layer**: HTTP status, canonical, index directives, robots and sitemap hints |
| 66 | - **Content & readability**: length, keyword coverage, duplication, thin or low‑value sections |
| 67 | - **Media & links**: image ALT attributes, internal link structure, external links / broken links |
| 68 | - **Brand & GEO signals**: favicon, brand / organization info, logo exposure, Schema.org markup |
| 69 | |
| 70 | 3. Highlight **high‑priority issues** that are likely to affect: |
| 71 | - indexability and crawling |
| 72 | - CTR and snippet quality |
| 73 | - perceived trust / authority |
| 74 | |
| 75 | 4. Provide concrete, implementable recommendations for each important issue, not just a restatement of the report. |
| 76 | |
| 77 | 5. Add a **GEO / RAG perspective**, for example: |
| 78 | - Is the page easy for a retrieval system to index and match semantically? |
| 79 | - Are there clear entity signals (Organization / Person / Product, etc.) that help LLMs trust this source? |
| 80 | - Does the page risk being treated as “thin / spammy / boilerplate” content? |
| 81 | |
| 82 | --- |
| 83 | |
| 84 | ## Recommended output structure |
| 85 | |
| 86 | When responding based on Fennec SEO Auditor results, the assistant should aim for a structure like: |
| 87 | |
| 88 | 1. **Page overview** |
| 89 | - URL, title, H1, target intent / query |
| 90 | |
| 91 | 2. **Issue summary (with priorities)** |
| 92 | - High / Medium / Low priority list |
| 93 | |
| 94 | 3. **Detailed findings and fixes** |
| 95 | - Meta & snippets (title, description, OG tags) |
| 96 | - Content & headings |
| 97 | - Internal links & anchors |
| 98 | - Technical / indexability |
| 99 | - Media (images, ALT text) |
| 100 | - Structured data & entity signals |
| 101 | |
| 102 | 4. **GEO / RAG perspective** |
| 103 | - How well this page can be retrieved, re‑ranked and cited by LLMs |
| 104 | - Additional suggestions (e.g. add FAQ schema, clarify sections, add data / sources) |
| 105 | |
| 106 | --- |
| 107 | |
| 108 | ## Notes and constraints |
| 109 | |
| 110 | - The assistant **does not** directly control the browser or extension; it relies on the user to run Fennec and share the output. |
| 111 | - Recommendations should balance: |
| 112 | - Classic SEO (crawlability, rankings, CTR, readability) |
| 113 | - GEO / LLM needs (structured signals, semantic clarity, trustworthy sources, clear entities) |
| 114 | - The assistant should avoid generic advice and tie recommendations back to: |
| 115 | - the user’s actual page |
| 116 | - the specific issues reported by Fennec SEO Auditor. |
People who liked this also viewed
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tagSkillsJul 2026
- copywritingWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user sSkillsJul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,'SkillsJul 2026
- content-strategyWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "conSkillsJul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pSkillsJul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing stratSkillsJul 2026
