seo-technical
SEO Technical
When to Use
- Running a technical SEO audit on an existing site.
- Diagnosing why pages are not being indexed or ranked.
- Optimizing Core Web Vitals or page speed.
- Setting up site architecture (sitemaps, robots.txt, canonicalization).
- Implementing structured data / schema markup.
- Managing AI crawler access via robots.txt.
- Preparing a new site or migration for SEO readiness.
- Reviewing JavaScript rendering and its impact on indexation.
Context Required
- From startup-context: product description, target audience, primary keywords, current domain and site structure.
- From the user: site URL, access to Google Search Console data (if available), specific pages of concern, known issues, tech stack (static site, SPA, WordPress, etc.), whether the site has been previously audited.
Workflow
Audit across 9 technical dimensions. Score on a 100-point scale with category breakdowns.
More from shawnpang/startup-founder-skills
terms-of-service
When the user needs to draft, review, or update terms of service for their SaaS product or web application.
65pitch-deck
When the user wants to create, review, or restructure a fundraising pitch deck for seed or Series A. Also activates when the user mentions "deck", "pitch", "investor presentation", or "slide structure".
55competitive-analysis
When the user needs to evaluate competitors, understand the competitive landscape, or position their product against alternatives.
53review-mining
When the user wants to research customer pain points, complaints, or sentiment using review platforms like Trustpilot, G2, Capterra, or app stores. Also use when the user mentions "what are users saying", "competitor reviews", "pain points", or "voice of customer research".
53data-room
When the user wants to prepare a due diligence data room for fundraising, or when an investor has requested additional materials after a pitch. Also activates for "data room", "due diligence", "DD checklist", or "what documents do investors need?".
51prd-writing
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
49