
Seo Aeo Audit
- 582 installs
- 818 repo stars
- Updated May 12, 2026
- warpdotdev/oz-skills
seo-aeo-audit is an agent skill that automatically audits product pages, documentation, and landing copy for traditional SEO and AI-search AEO visibility before launch.
About
seo-aeo-audit is a warpdotdev oz-skills checker for dual search visibility—classic SEO and answer-engine optimization (AEO) for AI citations. The skill reviews product pages, docs, and landing copy for metadata, structure, and self-contained answer sentences that ChatGPT, Perplexity, and Google AI Overviews can quote. Listed on skills.sh with 489 installs and rank 18 in its source collection, seo-aeo-audit targets developers shipping SaaS sites who need a structured pre-launch pass instead of manual checklist spreadsheets. Agents flag gaps in FAQ-shaped content, stat-backed facts, and query-shaped headings that retrieval engines reward. Run it when marketing copy is draft-complete but before public launch or major distribution pushes.
- Runs 40+ combined SEO and AEO checks in one pass
- Identifies missing schema, poor entity coverage, and weak answer-engine signals
- Produces prioritized fix list with confidence scores
- Outputs ready-to-use metadata and structured-data recommendations
- Works on markdown, HTML, and React/Next.js pages
Seo Aeo Audit by the numbers
- 582 all-time installs (skills.sh)
- +10 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #706 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/warpdotdev/oz-skills --skill seo-aeo-auditAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 582 |
|---|---|
| repo stars | ★ 818 |
| Last updated | May 12, 2026 |
| Repository | warpdotdev/oz-skills ↗ |
How do you audit pages for SEO and AEO before launch?
Automatically audit their product pages, docs, and landing copy for both traditional SEO and AI-search (AEO) visibility before launch.
Who is it for?
Developers launching SaaS product sites who need a structured SEO plus AEO audit on landing pages and documentation before go-live.
Skip if: Developers seeking paid ad campaign setup, backlink outreach automation, or audits of non-web artifacts like mobile app store listings only.
When should I use this skill?
A developer asks to audit landing copy, docs, or product pages for SEO, AEO, or AI-search citation readiness before launch.
What you get
SEO issue lists, AEO citation gaps, FAQ recommendations, and revised copy guidance for product and docs pages.
- SEO audit findings
- AEO recommendation lists
By the numbers
- Listed with 489 installs on skills.sh from warpdotdev/oz-skills
- Ranked 18 in the warpdotdev/oz-skills collection on skills.sh
Files
SEO Optimization
Search engine optimization based on Lighthouse SEO audits and Google Search guidelines. Focus on technical SEO, on-page optimization, and structured data.
Technical SEO
Crawlability
robots.txt:
# /robots.txt
User-agent: *
Allow: /
# Block admin/private areas
Disallow: /admin/
Disallow: /api/
Disallow: /private/
# Don't block resources needed for rendering
# ❌ Disallow: /static/
Sitemap: https://example.com/sitemap.xmlMeta robots:
<!-- Default: indexable, followable -->
<meta name="robots" content="index, follow">
<!-- Noindex specific pages -->
<meta name="robots" content="noindex, nofollow">
<!-- Indexable but don't follow links -->
<meta name="robots" content="index, nofollow">
<!-- Control snippets -->
<meta name="robots" content="max-snippet:150, max-image-preview:large">Canonical URLs:
<!-- Prevent duplicate content issues -->
<link rel="canonical" href="https://example.com/page">
<!-- Self-referencing canonical (recommended) -->
<link rel="canonical" href="https://example.com/current-page">
<!-- For paginated content -->
<link rel="canonical" href="https://example.com/products">
<!-- Or use rel="prev" / rel="next" for explicit pagination -->XML sitemap
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2024-01-15</lastmod>
<changefreq>daily</changefreq>
<priority>1.0</priority>
</url>
<url>
<loc>https://example.com/products</loc>
<lastmod>2024-01-14</lastmod>
<changefreq>weekly</changefreq>
<priority>0.8</priority>
</url>
</urlset>Sitemap best practices:
- Maximum 50,000 URLs or 50MB per sitemap
- Use sitemap index for larger sites
- Include only canonical, indexable URLs
- Update
lastmodwhen content changes - Submit to Google Search Console
URL structure
✅ Good URLs:
https://example.com/products/blue-widget
https://example.com/blog/how-to-use-widgets
❌ Poor URLs:
https://example.com/p?id=12345
https://example.com/products/item/category/subcategory/blue-widget-2024-sale-discountURL guidelines:
- Use hyphens, not underscores
- Lowercase only
- Keep short (< 75 characters)
- Include target keywords naturally
- Avoid parameters when possible
- Use HTTPS always
HTTPS & security
<!-- Ensure all resources use HTTPS -->
<img src="https://example.com/image.jpg">
<!-- Not: -->
<img src="http://example.com/image.jpg">Security headers for SEO trust signals:
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY---
On-page SEO
Title tags
<!-- ❌ Missing or generic -->
<title>Page</title>
<title>Home</title>
<!-- ✅ Descriptive with primary keyword -->
<title>Blue Widgets for Sale | Premium Quality | Example Store</title>Title tag guidelines:
- 50-60 characters (Google truncates ~60)
- Primary keyword near the beginning
- Unique for every page
- Brand name at end (unless homepage)
- Action-oriented when appropriate
Meta descriptions
<!-- ❌ Missing or duplicate -->
<meta name="description" content="">
<!-- ✅ Compelling and unique -->
<meta name="description" content="Shop premium blue widgets with free shipping. 30-day returns. Rated 4.9/5 by 10,000+ customers. Order today and save 20%.">Meta description guidelines:
- 150-160 characters
- Include primary keyword naturally
- Compelling call-to-action
- Unique for every page
- Matches page content
Heading structure
<!-- ❌ Poor structure -->
<h2>Welcome to Our Store</h2>
<h4>Products</h4>
<h1>Contact Us</h1>
<!-- ✅ Proper hierarchy -->
<h1>Blue Widgets - Premium Quality</h1>
<h2>Product Features</h2>
<h3>Durability</h3>
<h3>Design</h3>
<h2>Customer Reviews</h2>
<h2>Pricing</h2>Heading guidelines:
- Single
<h1>per page (the main topic) - Logical hierarchy (don't skip levels)
- Include keywords naturally
- Descriptive, not generic
Image SEO
<!-- ❌ Poor image SEO -->
<img src="IMG_12345.jpg">
<!-- ✅ Optimized image -->
<img src="blue-widget-product-photo.webp"
alt="Blue widget with chrome finish, side view showing control panel"
width="800"
height="600"
loading="lazy">Image guidelines:
- Descriptive filenames with keywords
- Alt text describes the image content
- Compressed and properly sized
- WebP/AVIF with fallbacks
- Lazy load below-fold images
Internal linking
<!-- ❌ Non-descriptive -->
<a href="/products">Click here</a>
<a href="/widgets">Read more</a>
<!-- ✅ Descriptive anchor text -->
<a href="/products/blue-widgets">Browse our blue widget collection</a>
<a href="/guides/widget-maintenance">Learn how to maintain your widgets</a>Linking guidelines:
- Descriptive anchor text with keywords
- Link to relevant internal pages
- Reasonable number of links per page
- Fix broken links promptly
- Use breadcrumbs for hierarchy
---
Structured data (JSON-LD)
Organization
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Company",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"sameAs": [
"https://twitter.com/example",
"https://linkedin.com/company/example"
],
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-555-123-4567",
"contactType": "customer service"
}
}
</script>Article
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Choose the Right Widget",
"description": "Complete guide to selecting widgets for your needs.",
"image": "https://example.com/article-image.jpg",
"author": {
"@type": "Person",
"name": "Jane Smith",
"url": "https://example.com/authors/jane-smith"
},
"publisher": {
"@type": "Organization",
"name": "Example Blog",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
},
"datePublished": "2024-01-15",
"dateModified": "2024-01-20"
}
</script>Product
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Blue Widget Pro",
"image": "https://example.com/blue-widget.jpg",
"description": "Premium blue widget with advanced features.",
"brand": {
"@type": "Brand",
"name": "WidgetCo"
},
"offers": {
"@type": "Offer",
"price": "49.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://example.com/products/blue-widget"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.8",
"reviewCount": "1250"
}
}
</script>FAQ
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What colors are available?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Our widgets come in blue, red, and green."
}
},
{
"@type": "Question",
"name": "What is the warranty?",
"acceptedAnswer": {
"@type": "Answer",
"text": "All widgets include a 2-year warranty."
}
}
]
}
</script>Breadcrumbs
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com"
},
{
"@type": "ListItem",
"position": 2,
"name": "Products",
"item": "https://example.com/products"
},
{
"@type": "ListItem",
"position": 3,
"name": "Blue Widgets",
"item": "https://example.com/products/blue-widgets"
}
]
}
</script>Validation
Test structured data at:
---
Mobile SEO
Responsive design
<!-- ❌ Not mobile-friendly -->
<meta name="viewport" content="width=1024">
<!-- ✅ Responsive viewport -->
<meta name="viewport" content="width=device-width, initial-scale=1">Tap targets
/* ❌ Too small for mobile */
.small-link {
padding: 4px;
font-size: 12px;
}
/* ✅ Adequate tap target */
.mobile-friendly-link {
padding: 12px;
font-size: 16px;
min-height: 48px;
min-width: 48px;
}Font sizes
/* ❌ Too small on mobile */
body {
font-size: 10px;
}
/* ✅ Readable without zooming */
body {
font-size: 16px;
line-height: 1.5;
}---
International SEO
Hreflang tags
<!-- For multi-language sites -->
<link rel="alternate" hreflang="en" href="https://example.com/page">
<link rel="alternate" hreflang="es" href="https://example.com/es/page">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/page">
<link rel="alternate" hreflang="x-default" href="https://example.com/page">Language declaration
<html lang="en">
<!-- or -->
<html lang="es-MX">---
SEO audit checklist
Critical
- [ ] HTTPS enabled
- [ ] robots.txt allows crawling
- [ ] No
noindexon important pages - [ ] Title tags present and unique
- [ ] Single
<h1>per page
High priority
- [ ] Meta descriptions present
- [ ] Sitemap submitted
- [ ] Canonical URLs set
- [ ] Mobile-responsive
- [ ] Core Web Vitals passing
Medium priority
- [ ] Structured data implemented
- [ ] Internal linking strategy
- [ ] Image alt text
- [ ] Descriptive URLs
- [ ] Breadcrumb navigation
Ongoing
- [ ] Fix crawl errors in Search Console
- [ ] Update sitemap when content changes
- [ ] Monitor ranking changes
- [ ] Check for broken links
- [ ] Review Search Console insights
---
Audit workflow
1. Baseline: run Lighthouse and PageSpeed on key templates (home, category, detail, blog). 2. Crawl: verify indexability, canonicals, and duplicate content (use Search Console + crawler). 3. Fix blockers: noindex, robots.txt, canonical mismatches, redirect chains. 4. On-page: titles, meta descriptions, headings, internal linking, image alt. 5. Structured data: add JSON-LD and validate rich results. 6. Re-verify: re-run Lighthouse/PageSpeed and check Search Console coverage.
---
Common pitfalls
noindexorX-Robots-Tagaccidentally set on important pagesrobots.txtblocks CSS/JS or critical render resources- Canonical points to a different URL than the one indexed
- Mixed
http/httpsorwww/non-wwwcausing duplicate content - Redirect chains/loops (waste crawl budget and slow page load)
- Parameterized URLs indexable (filters, sort, UTM) without canonical control
- JavaScript-rendered content not visible in initial HTML
- Soft 404s (200 status with "not found" content)
- Sitemap includes non-canonical or
noindexURLs - Hreflang tags missing reciprocal links or using wrong language/region codes
---
Tools
| Tool | Use |
|---|---|
| Google Search Console | Monitor indexing, fix issues |
| Google PageSpeed Insights | Performance + Core Web Vitals |
| Rich Results Test | Validate structured data |
| Lighthouse | Full SEO audit |
| Screaming Frog | Crawl analysis |
---
Scripts (optional)
Scripts under scripts/ for repeatable audits:
scripts/lighthouse.sh: run Lighthouse CLI against a URL or URL list and store JSON reports.scripts/pagespeed.sh: call PageSpeed Insights API withcurland capture JSON output.scripts/search-console-export.mjs: export Search Console Search Analytics data (requires OAuth access token).
Example usage:
# Lighthouse (SEO category only)
scripts/lighthouse.sh https://example.com
scripts/lighthouse.sh urls.txt reports/lighthouse
# PageSpeed Insights API (requires PAGESPEED_API_KEY)
PAGESPEED_API_KEY=... scripts/pagespeed.sh https://example.com
PAGESPEED_API_KEY=... scripts/pagespeed.sh urls.txt reports/pagespeed
# Search Console API (requires GSC_ACCESS_TOKEN)
GSC_ACCESS_TOKEN=... scripts/search-console-export.mjs https://example.com 2024-01-01 2024-01-31---
AEO / AI Visibility Optimization
Answer Engine Optimization (AEO) focuses on making content discoverable and citable by AI agents (ChatGPT, Perplexity, Gemini, Google AI Overviews). While SEO targets rankings and clicks, AEO targets citations, mentions, and brand authority within AI-generated responses.
Key differences from SEO
SEO: Rank high → get clicks → drive traffic
AEO: Be cited → own the answer → build authority
SEO metric: Position, CTR, impressions
AEO metric: Citations, mentions, AI visibility score
SEO query: "best project management software"
AEO query: "What's the best project management software for a remote team of 15 with budget under $500/month?"Market shift:
- Gartner predicts 25% drop in traditional search volume by 2026 due to AI chatbots
- 400M+ people use OpenAI products weekly
- 58% of searches are now "zero-click" (answered directly in AI interface)
Content structure for AEO
Answer-first formatting:
<!-- ❌ SEO-style (context first) -->
## What is AEO?
In recent years, the rise of AI-powered search has transformed
how users discover information. This shift has created new
opportunities for brands. Answer Engine Optimization is...
<!-- ✅ AEO-style (answer first) -->
## What is AEO?
Answer Engine Optimization (AEO) is the practice of structuring
content so AI systems can directly extract and cite answers.
It focuses on citations in AI responses rather than search rankings.
Unlike traditional SEO, AEO optimizes for conversational queries
and zero-click results where users get answers without visiting
your site.Guidelines:
- Lead with 40-60 word direct answer
- Self-contained responses (AI extracts without surrounding context)
- Conversational, natural language
- Specific data > vague claims
- Include quantified claims, dates, authoritative citations
Entity-based optimization:
<!-- ❌ Keyword-focused -->
"Our software helps teams collaborate better with features
for project management and communication."
<!-- ✅ Entity-focused -->
"Acme PM is a project management platform for remote teams.
Founded in 2020, serves 50,000+ companies. Key features:
Kanban boards, time tracking, Slack integration. Pricing:
$12/user/month."Define who you are, what you do, and why AI should trust you.
Schema for AEO
Expand beyond SEO schema to optimize for AI extraction.
Critical schema types for AEO:
1. FAQPage (highest AI citation rate)
- Template:
references/json-ld-templates.md
FAQ answer guidelines for AEO:
- 40-60 words ideal (under 30 = lacks substance, over 80 = hard to extract)
- Match visible H2/H3 headings to schema "name" property exactly
- Include specific numbers, dates, and data
- Self-contained (makes sense without context)
- Natural question phrasing (how users actually ask)
2. Author + Organization (trust signals)
- Template:
references/json-ld-templates.md
Why it matters: AI engines prioritize content from identifiable, authoritative sources. Use sameAs links to disambiguate your brand.
3. Product (for e-commerce AEO)
- Template:
references/json-ld-templates.md
Allows AI shopping modules to show accurate pricing, availability, reviews.
Platform-specific optimization
Different AI engines have different preferences. Balance all three for maximum citation probability.
ChatGPT:
- Neutral, encyclopedia-style tone
- Authoritative external citations
- Specific data and quantified claims
- Formal structure
Example: "According to a 2025 Gartner study, 78% of enterprises
adopted AI-powered search tools. The primary drivers were cost
reduction (cited by 62% of respondents) and improved accuracy
(58%). Source: Gartner AI Search Report 2025."Perplexity:
- Conversational, experience-driven
- Practical examples and case studies
- Community insights and real-world context
- Less formal tone
Example: "Most teams start with the free tier and upgrade after
2-3 months once they've proven ROI. Based on feedback from 500+
customers, common triggers for upgrading include hitting user
limits or needing advanced reporting."Google AI Overviews:
- E-E-A-T signals (Experience, Expertise, Authoritativeness, Trust)
- Fresh content with recent dates
- Featured snippet-friendly formatting
- Mobile-optimized structure
Example: "Updated February 2026: Current pricing starts at
$12/user/month (annual billing). Month-to-month adds 20%.
Education and nonprofit discounts available. No free tier
as of Q1 2026."AEO measurement & tools
Metrics:
- Citation frequency (how often AI mentions your brand)
- Visibility score (presence across AI platforms)
- Context quality (positive/neutral/negative sentiment)
- Source attribution (which URLs AI cites)
Tracking AI referral traffic:
In Google Analytics 4, filter traffic sources:
chat.openai.com(ChatGPT)perplexity.aigemini.google.comcopilot.microsoft.com
Monitor these as separate acquisition sources.
Use your preferred AEO monitoring tool to track citation frequency, context, and source attribution.
AEO audit checklist
Content audit
- [ ] All key pages have 40-60 word direct answers upfront
- [ ] FAQ sections with self-contained answers
- [ ] Conversational language matching natural queries
- [ ] Specific data (numbers, dates, sources) not vague claims
- [ ] Author bios and organization info visible
- [ ] Content updated with recent dates (freshness)
Schema audit
- [ ] FAQPage schema on FAQ/guide pages
- [ ] Author schema on all articles/blogs
- [ ] Organization schema site-wide
- [ ] Product schema on product pages (if e-commerce)
- [ ] Article schema with datePublished/dateModified
- [ ] Schema matches visible content exactly (no hidden markup)
- [ ] Validate with Google Rich Results Test
Technical audit
- [ ] JSON-LD format (preferred by AI engines)
- [ ] Schema.org standards compliance
- [ ] No conflicting or duplicate schema
- [ ] Fast page load (AI crawlers prefer fast sites)
- [ ] Clean HTML structure (semantic headings)
- [ ] Mobile-optimized (especially for Google AI Overviews)
Entity & authority signals
- [ ] Clear brand identity (who you are, what you do)
- [ ] Consistent NAP (name, address, phone) across web
- [ ]
sameAslinks to LinkedIn, Twitter, official profiles - [ ] External citations and backlinks from authoritative sources
- [ ] Active presence on review platforms
- [ ] Google Business Profile optimized (local businesses)
AI visibility monitoring
- [ ] Test top 10-20 commercial queries monthly
- [ ] Track AI referral traffic in GA4
- [ ] Monitor brand mentions across AI platforms
- [ ] Check citation context (positive/neutral/negative)
- [ ] Verify factual accuracy of AI responses about your brand
- [ ] Set up alerts for visibility changes (if using paid tools)
---
References
- Google Search Central
- Schema.org
- Core Web Vitals
- Web Quality Audit
JSON-LD templates
FAQPage
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "What is the average cost of local SEO services?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most small businesses invest $1,000–$3,000/month for local SEO covering technical fixes, Google Business Profile optimization, citations, and content. Budgets vary with competition and practice areas. Ask providers for transparent deliverables, local proof, and expected timelines."
}
}]
}
</script>Author + Organization
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"author": {
"@type": "Person",
"name": "Jane Smith",
"url": "https://example.com/authors/jane-smith",
"sameAs": [
"https://linkedin.com/in/janesmith",
"https://twitter.com/janesmith"
]
},
"publisher": {
"@type": "Organization",
"name": "Example Corp",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
},
"sameAs": [
"https://linkedin.com/company/example",
"https://twitter.com/examplecorp"
]
},
"datePublished": "2026-01-15",
"dateModified": "2026-02-01"
}
</script>Product
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Acme Project Manager Pro",
"description": "Cloud project management for remote teams. Kanban, time tracking, 200+ integrations.",
"brand": {
"@type": "Brand",
"name": "Acme Software"
},
"offers": {
"@type": "Offer",
"price": "12.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"priceValidUntil": "2026-12-31"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.7",
"reviewCount": "3240"
}
}
</script>#!/usr/bin/env bash
set -euo pipefail
if ! command -v lighthouse >/dev/null 2>&1; then
echo "lighthouse CLI not found. Install with: npm i -g lighthouse" >&2
exit 1
fi
if [ "$#" -lt 1 ]; then
echo "Usage: scripts/seo/lighthouse.sh <url|urls.txt> [output_dir]" >&2
exit 1
fi
INPUT="$1"
OUTPUT_DIR="${2:-reports/lighthouse}"
mkdir -p "$OUTPUT_DIR"
run_lighthouse() {
local url="$1"
local safe_name
safe_name=$(echo "$url" | sed -E 's#https?://##; s#[^a-zA-Z0-9._-]#_#g')
local out_path="$OUTPUT_DIR/${safe_name}.json"
echo "Running Lighthouse (SEO) for $url"
lighthouse "$url" \
--only-categories=seo \
--output=json \
--output-path="$out_path" \
--quiet
}
if [ -f "$INPUT" ]; then
while IFS= read -r url; do
[ -z "$url" ] && continue
run_lighthouse "$url"
done < "$INPUT"
else
run_lighthouse "$INPUT"
fi
echo "Reports saved to $OUTPUT_DIR"
#!/usr/bin/env bash
set -euo pipefail
if [ "$#" -lt 1 ]; then
echo "Usage: scripts/seo/pagespeed.sh <url|urls.txt> [output_dir]" >&2
exit 1
fi
if [ -z "${PAGESPEED_API_KEY:-}" ]; then
echo "Missing PAGESPEED_API_KEY env var." >&2
echo "Get an API key from Google Cloud Console, then run:" >&2
echo " PAGESPEED_API_KEY=... scripts/seo/pagespeed.sh https://example.com" >&2
exit 1
fi
INPUT="$1"
OUTPUT_DIR="${2:-reports/pagespeed}"
mkdir -p "$OUTPUT_DIR"
urlencode() {
python3 - <<'PY' "$1"
import sys, urllib.parse
print(urllib.parse.quote(sys.argv[1], safe=""))
PY
}
run_pagespeed() {
local url="$1"
local safe_name
safe_name=$(echo "$url" | sed -E 's#https?://##; s#[^a-zA-Z0-9._-]#_#g')
local out_path="$OUTPUT_DIR/${safe_name}.json"
local encoded_url
encoded_url=$(urlencode "$url")
echo "Running PageSpeed Insights (SEO) for $url"
curl -sS \
"https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=${encoded_url}&category=SEO&category=PERFORMANCE&strategy=mobile&key=${PAGESPEED_API_KEY}" \
-o "$out_path"
}
if [ -f "$INPUT" ]; then
while IFS= read -r url; do
[ -z "$url" ] && continue
run_pagespeed "$url"
done < "$INPUT"
else
run_pagespeed "$INPUT"
fi
echo "Reports saved to $OUTPUT_DIR"
#!/usr/bin/env node
import fs from "node:fs";
import path from "node:path";
const args = process.argv.slice(2);
const [siteUrl, startDate, endDate] = args;
if (!siteUrl || !startDate || !endDate) {
console.error(
"Usage: scripts/seo/search-console-export.mjs <siteUrl> <startDate> <endDate> [outputDir]"
);
console.error("Example: scripts/seo/search-console-export.mjs https://example.com 2024-01-01 2024-01-31");
process.exit(1);
}
const outputDir = args[3] || "reports/search-console";
const token = process.env.GSC_ACCESS_TOKEN;
if (!token) {
console.error("Missing GSC_ACCESS_TOKEN env var.");
console.error("Create an OAuth 2.0 access token with Search Console API scope:");
console.error(" https://www.googleapis.com/auth/webmasters.readonly");
console.error("Then run:");
console.error(" GSC_ACCESS_TOKEN=... scripts/seo/search-console-export.mjs <siteUrl> <start> <end>");
process.exit(1);
}
fs.mkdirSync(outputDir, { recursive: true });
const safeName = siteUrl.replace(/^https?:\/\//, "").replace(/[^a-zA-Z0-9._-]/g, "_");
const outPath = path.join(outputDir, `${safeName}_${startDate}_${endDate}.json`);
const endpoint = `https://searchconsole.googleapis.com/v1/sites/${encodeURIComponent(
siteUrl
)}/searchAnalytics/query`;
const body = {
startDate,
endDate,
dimensions: ["query", "page"],
rowLimit: 25000,
};
const res = await fetch(endpoint, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: `Bearer ${token}`,
},
body: JSON.stringify(body),
});
if (!res.ok) {
const text = await res.text();
console.error(`Search Console API error: ${res.status}`);
console.error(text);
process.exit(1);
}
const json = await res.json();
fs.writeFileSync(outPath, JSON.stringify(json, null, 2));
console.log(`Export saved to ${outPath}`);
Related skills
How it compares
Use seo-aeo-audit for pre-launch page copy checks; pair with analytics skills post-launch to measure traffic rather than citation-ready structure.
FAQ
What does seo-aeo-audit check beyond traditional SEO?
seo-aeo-audit evaluates answer-engine optimization—self-contained sentences, FAQ pairs, and stat-backed facts—that ChatGPT, Perplexity, and Google AI can cite, alongside standard metadata and heading structure.
When should developers run seo-aeo-audit?
Developers should run seo-aeo-audit after product pages and docs are draft-complete but before public launch, when AI-search and organic discoverability still can be fixed without post-launch rework.