TypingMindTypingMindThe best frontend for AI
Website Audit logo

Website Audit

Community
flitzrrr
website-audit

Systematic website analysis, relaunch planning, SEO migration, content audit, and post-launch monitoring for data-driven relaunches.

Overview

Publisherflitzrrr
Repositoryfrontend-design-skills
Skill namewebsite-audit
Stars
9
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by flitzrrr on GitHub. Read the source before you install it.

Installation

Install the Website Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/flitzrrr/frontend-design-skills/tree/main/skills-src/website-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/flitzrrr/frontend-design-skills.git /tmp/frontend-design-skills
mkdir -p .claude/skills
cp -r /tmp/frontend-design-skills/skills-src/website-audit .claude/skills/website-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Website Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Website Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Website Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Website Audit and Relaunch

No relaunch without thorough analysis. Blind redevelopment repeats old mistakes. Analysis before action, data before opinions.

Scope

Use this skill when you:

  • Systematically analyze an existing website
  • Plan and structure a relaunch
  • Conduct a content audit
  • Prepare an SEO migration
  • Set up post-launch monitoring
  • Create a quick initial assessment (quick audit)

Principles

1. Analysis Before Action

No relaunch without thorough analysis of the existing website.

2. Relaunch Is Not Redesign

A redesign polishes the surface. A relaunch reworks content, technology, structure, AND design holistically.

3. Data Over Opinions

Decisions are based on analytics, user feedback, and technical measurements.

4. Visitor Needs Meet Business Goals

A successful relaunch serves visitors better AND supports business objectives more effectively.

5. Nothing Works Without a Content Strategy

The best layouts are useless with outdated, irrelevant content.

6. Preserve SEO Continuity

A relaunch that destroys rankings is an expensive setback. Redirects and SEO migration are mandatory.

7. A Relaunch Is Not an End in Itself

"We need something new" is not a goal. Concrete, measurable objectives come before the first wireframe.

Rules

DO: Systematically Work Through the 5 Analysis Dimensions

1. Technical Analysis: Load times (PageSpeed, GTmetrix), mobile usability, broken links, HTTPS, CMS currency.

2. Usability Analysis: Navigation paths, forms on all devices, CTA visibility, search functionality, Nielsen heuristics.

3. Content Analysis: Currency, user relevance, structure (subheadings, paragraphs), duplicates, content gaps.

4. SEO Analysis: Keyword rankings, meta titles/descriptions, internal linking, crawling errors, backlink profile.

5. Conversion Analysis: Conversion goals and current rates, user flow, drop-off rates, heatmaps, and session recordings.

See references/audit-checklisten.md for details and templates for each dimension.

DO: Clarify Internally Before the Relaunch

  • Timeline: When should the new website go live?
  • Budget: What is realistically available?
  • Points of Contact: Who decides, who delivers content?
  • Hosting and Access: Where is the website hosted, who has credentials?
  • Internal Capacity: Can the team contribute?

DO: Conduct a Content Audit Before the Relaunch

  • INVENTORY all content (text, images, downloads, videos).
  • CATEGORIZE: Keep / Revise / Delete / Create new.
  • CRITERIA: Currency, relevance, SEO performance, quality.

DO: Conduct a Competitive Analysis

  • ANALYZE at least 3–5 direct competitors.
  • EVALUATE: Design, content, features, site structure, SEO visibility.
  • DOCUMENT: What are others doing better? Where are the gaps?

DO: Plan the SEO Migration

  • DOCUMENT all existing URLs.
  • CREATE 301 redirects for every URL that changes.
  • PROTECT existing rankings and backlinks.
  • MONITOR Google Search Console after launch.
  • UPDATE sitemap and robots.txt.

DO: Define Measurable Relaunch Goals

Examples: Load time under 3 seconds, 20% more organic traffic within 6 months, doubling newsletter sign-ups, reducing bounce rate by 15%.

DON'T: Try to Redo Everything

  • Identify what works and carry it over.
  • Migrate pages with strong rankings with particular care.

DON'T: Launch Without a Testing Phase

  • Test before go-live: Functional, visual, across devices, SEO-related.

DON'T: Forget SEO Redirects

  • Every old URL needs a 301 redirect. Forgotten redirects = lost rankings.

DON'T: Stop After Launch

  • The relaunch is the beginning. Monitoring, optimization, and content maintenance are ongoing responsibilities.

Patterns

Relaunch Process (7 Phases)

  1. Analysis (5 dimensions), 2. Strategy (goals, positioning, content), 3. Concept (IA, wireframes), 4. Design, 5. Implementation (development, content, SEO), 6. Testing (QA, cross-browser, performance), 7. Launch and monitoring. See references/relaunch-phasen.md for details.

Quick Audit (2 Hours)

For an initial assessment: 1. PageSpeed test (15 min), 2. Mobile check on 3 devices (15 min), 3. Navigation and key pages (30 min), 4. Quick SEO check (30 min), 5. Test conversion path (15 min), 6. 5-point summary (15 min).

Content Migration Matrix

For large volumes: Table with old URL, new URL, redirect, status, responsible person, deadline.

Post-Launch Monitoring (30-60-90 Days)

  • Days 1–7: Daily: 404 errors, crawling, redirects, uptime.
  • Days 8–30: Weekly: Rankings, traffic, conversions, user feedback.
  • Days 31–60: Bi-weekly: Comparison with pre-launch baseline.
  • Days 61–90: Monthly: ROI assessment, prioritize optimizations.

Stakeholder Relaunch Briefing

At kickoff: One-pager with current state, reasons, goals (measurable), budget, timeline, responsibilities, decision-making process.

Anti-Patterns

The "We Need Something New" Relaunch

Relaunch without concrete goals. Significant effort, no measurable progress. Solution: At least 3 measurable goals before the first wireframe.

The Tech-First Relaunch

New CMS adopted, everything else "will work itself out." New technology, same old problems. Solution: Content strategy and concept first, then technology selection.

The Forgotten SEO Migration

New URLs without redirects. Ranking loss, traffic collapse. Recovery takes months. Solution: URL mapping, 301 redirects, post-launch verification.

The Never-Ending Relaunch

Scope grows constantly, no end in sight. Solution: Fixed scope and timeline. MVP approach: core pages first, then iterative expansion.

Analysis Paralysis

Endless analysis without implementation. Solution: Limit the analysis phase to 2–4 weeks. "Good enough" is sufficient for informed decisions.

Checklist

Before the Relaunch

  • Technical analysis completed
  • Usability analysis conducted
  • Content audit with categorization
  • SEO analysis: rankings, meta data, backlinks documented
  • Conversion analysis: current rates as baseline
  • Competitive analysis with 3–5 competitors
  • Measurable relaunch goals defined
  • URL mapping for SEO migration created

During the Relaunch

  • Content strategy established before design
  • Wireframes approved
  • 301 redirects configured and tested
  • Sitemap and robots.txt updated
  • Cross-browser and cross-device testing
  • Performance budget met (load time under 3 sec.)

After the Relaunch

  • 404 errors monitored daily (week 1)
  • Redirects spot-checked
  • Google Search Console checked for indexing issues
  • Conversion rates compared against baseline (30 days)
  • Organic traffic compared against baseline (60 days)
  • Optimization measures prioritized for the next 90 days

Cross-References

  • customer-journey — Journey analysis is a core component of the audit
  • design-process — The relaunch follows the design process starting from the concept phase
  • ai-design-workflow — AI tools can accelerate analysis and content migration
  • landing-pages — Existing landing pages are part of the audit scope
  • usability — Usability analysis as one of the 5 audit dimensions
  • webdesign-review — Review methodology for the analysis phase

Frequently asked questions

What does the Website Audit AI skill do?

Systematic website analysis, relaunch planning, SEO migration, content audit, and post-launch monitoring for data-driven relaunches.

Why use Website Audit on TypingMind?

Because you install it once and use it with any model. Website Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Website Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/flitzrrr/frontend-design-skills/tree/main/skills-src/website-audit. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Website Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Website Audit?

As many as you like. As long as a model supports skills, you can use Website Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Website Audit AI skill free?

Yes. It is published on GitHub by flitzrrr under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
mattpocock logo

Grill Me

mattpocock
CommunityPopular

A relentless interview to sharpen a plan or design.

23K
273.1K
1 files
View
affaan-m logo

Brand Discovery

affaan-m
CommunityPopular

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

40.4K
270.2K
9 files
View
affaan-m logo

Competitive Platform Analysis

affaan-m
CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

40.4K
270.2K
1 files
View
affaan-m logo

Frontend Slides

affaan-m
CommunityPopular

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a…

40.4K
270.2K
2 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇