This is the document we give Claude Code when it builds a website for us. 9 stages, from infrastructure to quality control, with mandatory checks and a stop for approval at the end of each stage.
User instructions: what to prepare before you start
Before you give this checklist to Claude Code, prepare the following details and paste them in together with the document:
Required details
Site name in Hebrew: [e.g.: פנלדין (PneLeDin), a lawyers portal]
Site name in English: [e.g.: PneLeDin]
Domain: [e.g.: pneledin.co.il]
Niche / field: [e.g.: lawyers, buying an apartment, car insurance]
Site language: [Hebrew / English / bilingual]
Recommended details (the more you fill in, the more accurate the output)
Primary color: [e.g.: #2563EB]
Secondary color: [e.g.: #F59E0B]
Background color: [e.g.: #FFFFFF]
Text color: [e.g.: #1F2937]
Font: [e.g.: Heebo / Assistant / Rubik]
Competitor site for reference: [URL]
Target audience: [e.g.: people looking for a divorce lawyer]
List of main categories: [e.g.: family law, employment law, real estate law]
List of cities (if relevant): [e.g.: Tel Aviv, Jerusalem, Haifa, Beersheba]
How to use it: copy this entire document + the details you filled in above, and paste it into Claude Code. Claude Code will work through the steps one after another.
Instructions for Claude Code: start here
You are going to build an SEO-optimized static site from scratch. Work through the following steps in order. Do not skip steps. Do not build everything in a single command. At the end of each step, report to the user what was completed and ask whether to continue to the next step.
Step 1: Project infrastructure setup
1.1 Create the folder structure
project-root/
├── index.html
├── css/
│ └── style.css
├── js/
│ └── main.js
├── pages/
│ ├── categories/
│ ├── articles/
│ ├── guides/
│ ├── locations/
│ └── legal/
├── assets/
│ ├── images/
│ └── icons/
├── sitemap.xml
├── robots.txt
├── manifest.json
└── favicon.ico
1.2 Define CSS Variables
Define the variables at the top of the CSS file based on the details the user provided:
• Colors: --primary, --secondary, --bg, --text, --text-light, --border, --card-bg
• Fonts: --font-main with a sans-serif fallback
• Weights: --fw-regular: 400, --fw-medium: 500, --fw-bold: 700, --fw-extra: 800
• Spacing: --spacing-xs through --spacing-3xl
• Radii: --radius-sm, --radius-md, --radius-lg, --radius-full
• Shadows: --shadow-sm, --shadow-md, --shadow-lg
• Transitions: --transition-fast: 0.2s ease, --transition-normal: 0.3s ease
1.3 CSS Reset + Typography
• Apply a CSS Reset (box-sizing, margin, padding)
• Set base typography: H1-H6 sizes, paragraphs, links
• Define buttons: .btn-primary, .btn-secondary, .btn-outline
• Define a responsive Grid System: .grid-2, .grid-3, .grid-4
• Define a Card Component: .card with a hover effect
1.4 Required checks at the end of the step
• [ ] All CSS Variables are defined and working
• [ ] CSS Reset is active
• [ ] The font loads from Google Fonts with font-display: swap and preconnect
• [ ] Responsive Grid works at 3 breakpoints: Desktop (~1024px), Tablet (~768px), Mobile (~480px)
Report to the user: "Step 1 complete: CSS infrastructure, fonts, Grid System. Continue to step 2?"
Step 2: Header + Footer + base template
2.1 Header
• Build a fixed Header (position: sticky) with:
• Logo (site name as text if there is no logo), linked to the home page
• Main navigation menu with links to all Hub pages
• Mobile hamburger menu with a smooth animation
• Header changes style on scroll (class scrolled)
• Add a hidden "Skip to content" link (skip-link) that appears on focus
2.2 Footer
• Build a Footer with:
• Logo + short site description
• Links to main pages (split into columns)
• Contact details: phone, email, address
• Social media buttons (inline SVG)
• Credit line + terms of use + privacy policy
2.3 Base HTML template
Create an HTML template that every page will use, including:
<!DOCTYPE html>
<html lang="he" dir="rtl">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>[Unique title] | [Site name]</title>
<meta name="description" content="[Unique description, 120-160 characters]">
<meta name="robots" content="index, follow">
<link rel="canonical" href="[Full page URL]">
<!-- Open Graph -->
<meta property="og:title" content="[Title]">
<meta property="og:description" content="[Description]">
<meta property="og:image" content="[Image URL]">
<meta property="og:url" content="[URL]">
<meta property="og:locale" content="he_IL">
<!-- Twitter -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="[Title]">
<meta name="twitter:description" content="[Description]">
<!-- Fonts -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=[FONT]:wght@400;500;700;800&display=swap" rel="stylesheet">
<!-- Critical CSS inline -->
<style>/* Critical CSS for Header + Hero */</style>
<!-- Main CSS -->
<link rel="stylesheet" href="/css/style.min.css">
<!-- Favicon -->
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="manifest" href="/manifest.json">
</head>
<body>
<a href="#main-content" class="skip-link">Skip to content</a>
<header role="banner"><!-- Header --></header>
<main id="main-content" role="main"><!-- Page content --></main>
<footer role="contentinfo"><!-- Footer --></footer>
<!-- JS -->
<script src="/js/main.min.js" defer></script>
</body>
</html>
2.4 Base JavaScript
Write the following functions in main.js:
• Mobile Menu: open/close the hamburger menu
• Scroll Header: add the scrolled class to the Header on scroll
• FAQ Accordion: open/close questions and answers
• Back-to-top: a back-to-top button that appears after scrolling
• Counter Animation: number counters with IntersectionObserver
• Fade-in Animation: elements animate in on scroll (IntersectionObserver)
• Scroll listeners with passive: true
2.5 Required checks at the end of the step
• [ ] Header displays correctly on desktop and mobile
• [ ] Hamburger menu opens and closes
• [ ] Header changes style on scroll
• [ ] Footer displays with all elements
• [ ] Skip-link works
• [ ] All JavaScript runs with no console errors
• [ ] Semantic HTML: <header>, <nav>, <main>, <footer> with role and aria-label
Report to the user: "Step 2 complete: Header, Footer, Template, base JS. Continue to step 3?"
Step 3: Home page
3.1 Hero Section
• H1 heading with the main keyword
• Description (paragraph) with a secondary keyword
• Main CTA button
• Optional: search bar / form
3.2 Additional sections
• Main categories: Cards Grid with SVG icons, title, short description, and a link to the category page
• Number counters: 3-4 animated Counters (IntersectionObserver)
• Informational content: a section with relevant SEO text
• FAQ: 5-8 questions in an Accordion
3.3 Floating CTA
A fixed (floating) CTA button that stays visible while scrolling and does not block content
3.4 Schema Markup (JSON-LD)
Add inside <script type="application/ld+json">:
[
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "[Site name]",
"url": "[URL]",
"potentialAction": {
"@type": "SearchAction",
"target": "[URL]/search?q={search_term_string}",
"query-input": "required name=search_term_string"
}
},
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "[Site name]",
"url": "[URL]",
"logo": "[Logo URL]",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "[Phone]",
"contactType": "customer service",
"areaServed": "IL",
"availableLanguage": "Hebrew"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "[Question]",
"acceptedAnswer": {
"@type": "Answer",
"text": "[Answer]"
}
}
]
}
]
3.5 Required checks at the end of the step
• [ ] A single H1 on the page
• [ ] All categories link to pages (even if the pages don't exist yet, create a placeholder)
• [ ] Counters work with animation
• [ ] FAQ Accordion opens and closes
• [ ] Floating CTA does not block content
• [ ] Schema is valid: check the JSON-LD structure
• [ ] Meta tags: title, description, canonical, OG, Twitter
Report to the user: "Step 3 complete: home page with Hero, categories, counters, FAQ, Schema. Continue to step 4?"
Step 4: Category pages (Hub Pages) + internal content pages
4.1 Hub page (main category page)
• Page Header with H1 + description + Breadcrumbs
• Grid of cards, each card linking to an internal content page
• Each card includes: icon/image, H2 title, short description, link
• Category-specific FAQ with schema
4.2 Internal content pages
Each internal page includes:
• Page Header: unique H1 + Breadcrumbs
• Content Layout: main content (70-75%) + Sidebar (25-30%)
• Main content: in-depth text with H2/H3, paragraphs, lists
• Sidebar:
• Quick navigation widget (links to pages in the same category)
• CTA Box
• Related links (cross-category)
• Topic-specific FAQ with schema
• Internal links: natural in-text links to other pages on the site
4.3 Cross-Linking
• Each internal page links to 2-3 pages from other categories
• Sidebar includes "Related topics" from different categories
• Breadcrumbs: Home > Category > Current page
4.4 Schema Markup for each internal page
[
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Home", "item": "[URL]"},
{"@type": "ListItem", "position": 2, "name": "[Category]", "item": "[Category URL]"},
{"@type": "ListItem", "position": 3, "name": "[Current page]", "item": "[Current URL]"}
]
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [...]
}
]
4.5 Required checks at the end of the step
• [ ] Every Hub Page links correctly to internal pages
• [ ] Every internal page: unique H1, unique meta title, unique meta description, canonical
• [ ] Breadcrumbs work and link correctly
• [ ] Sidebar displays correctly on desktop and drops below the content on mobile
• [ ] Cross-linking: every page links to pages from other categories
• [ ] Schema: BreadcrumbList + FAQPage on every page
• [ ] No duplicate (copy-paste) content between pages
Report to the user: "Step 4 complete: [X] category pages + [Y] internal pages. Continue to step 5?"
Step 5: Location / GEO pages (if relevant)
Note: skip this step if the user did not specify cities/locations in the brief.
5.1 Cities Hub page
• Page Header with H1 + description
• Grid of city cards
• Each card: city name, short description, link to the city page
5.2 City pages
Each city page includes:
• Unique H1 with the city name + niche (e.g.: "Lawyers in Tel Aviv")
• Location-specific content, not copy-paste with only the city name changed
• Links to relevant content categories
• Sidebar with other cities
• City-specific FAQ
• Schema: BreadcrumbList + LocalBusiness (if relevant)
5.3 Cross-Linking cities ↔ categories
• Each city page links to relevant content categories
• Each category page links to relevant cities
• Sidebar: "More cities" + "Related fields"
5.4 Required checks at the end of the step
• [ ] Every city page: unique H1, unique content, unique meta tags
• [ ] Cities ↔ categories cross-linking works
• [ ] Valid Schema on every city page
• [ ] No duplicate content between city pages
Report to the user: "Step 5 complete: [X] city pages. Continue to step 6?"
Step 6: Articles and guides
6.1 Articles Hub page
• Page Header + H1
• Grid of article cards: image/icon, title, date, excerpt, link
6.2 Article template
• Page Header + Breadcrumbs
• Publication date + author name
• Table of contents (TOC) with Anchor Links, if the article is long
• Text with H2/H3, paragraphs, lists
• Author Box at the bottom
• "Related articles": 3 relevant articles
• Schema: Article + BreadcrumbList
6.3 Guide template
• Same as an article, but with:
• TOC with Anchor Links (required)
• Split into chapters (H2 for each chapter)
• Highlighted tips (tip boxes)
• CTAs between chapters
• Schema: Article (subtype: Guide) + BreadcrumbList
6.4 Required checks at the end of the step
• [ ] Every article: unique H1, unique meta tags, unique content
• [ ] TOC with Anchor Links works (links jump to sections)
• [ ] Author Box displays
• [ ] "Related articles" link correctly
• [ ] Schema: Article + BreadcrumbList on every article
Report to the user: "Step 6 complete: [X] articles + [Y] guides. Continue to step 7?"
Step 7: Support pages (About, Contact, FAQ, legal)
7.1 About page
• Story, values, features (Features Grid)
• CTA to get in touch
7.2 Contact page
• Contact form (name, phone, email, message)
• Contact Grid: phone, email, address
• Map (Google Maps iframe or placeholder)
7.3 Main FAQ page
• FAQ search (real-time filtering)
• Filter by category
• Accordion for each question
• Schema: FAQPage
7.4 Legal pages
• Terms of use
• Privacy policy
• meta robots: noindex, follow
7.5 Required checks at the end of the step
• [ ] Contact form works (client-side validation)
• [ ] FAQ search filters in real time
• [ ] Legal pages have noindex
• [ ] FAQPage Schema on the main FAQ page
Report to the user: "Step 7 complete: support pages. Continue to step 8?"
Step 8: Technical SEO + files
8.1 sitemap.xml
Create a sitemap.xml with every page on the site:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>[Home page URL]</loc>
<lastmod>[Today's date in YYYY-MM-DD format]</lastmod>
<changefreq>weekly</changefreq>
<priority>1.0</priority>
</url>
<!-- Hub Pages: priority 0.8 -->
<!-- Content Pages: priority 0.6 -->
<!-- Articles: priority 0.6 -->
<!-- Location Pages: priority 0.5 -->
<!-- Support Pages: priority 0.3 -->
</urlset>
8.2 robots.txt
User-agent: *
Allow: /
Disallow: /assets/
Sitemap: [URL]/sitemap.xml
8.3 manifest.json
{
"name": "[Site name]",
"short_name": "[Short name]",
"start_url": "/",
"display": "standalone",
"background_color": "[Background color]",
"theme_color": "[Primary color]",
"icons": [
{"src": "/favicon.ico", "sizes": "32x32", "type": "image/x-icon"}
]
}
8.4 llms.txt (optional)
Create an llms.txt file in the root folder describing the site structure for AI models.
8.5 Required checks at the end of the step
• [ ] sitemap.xml includes every page on the site (count and verify)
• [ ] robots.txt is valid
• [ ] manifest.json is valid
Report to the user: "Step 8 complete: technical files. Continue to step 9, final quality check?"
Step 9: Final quality control (QA)
This is the most important step. Go through every check one by one and fix any issue you find.
9.1 Internal link check
Go through every page and check:
• [ ] All links in the main navigation (Header) work and point to the right page
• [ ] All Footer links work
• [ ] Breadcrumbs link correctly on every internal page
• [ ] Cards link to the right pages
• [ ] Sidebar links work and point to relevant pages
• [ ] Logo returns to the home page from every page
• [ ] No broken links (404): check every link
To check: run a script that goes through all HTML files, extracts every href, and verifies that each target file exists. Report to the user how many links are valid and how many are broken.
9.2 Content check
• [ ] Unique content on every page (no copy-paste between pages)
• [ ] Unique H1 headings: only one per page
• [ ] Correct heading hierarchy: H1 → H2 → H3 (don't skip levels)
• [ ] Consistent contact details across the whole site
9.3 Meta Tags check
Go through every page and check:
• [ ] Unique <title> on every page (50-60 characters, keyword at the start)
• [ ] Unique meta description on every page (120-160 characters)
• [ ] Correct canonical on every page
• [ ] og:title, og:description, og:url are set
• [ ] meta robots: index, follow for public pages, noindex for legal pages
9.4 Schema check
• [ ] Valid JSON-LD Schema (no syntax errors)
• [ ] Home page: WebSite + Organization + FAQPage
• [ ] Internal pages: BreadcrumbList + FAQPage
• [ ] Articles: Article + BreadcrumbList
• [ ] Cities: BreadcrumbList (+ LocalBusiness if relevant)
9.5 Design and responsiveness check
• [ ] Correct RTL: everything right-aligned, borders on the correct side
• [ ] Color consistency with the brand palette
• [ ] Sidebar drops below the main content on mobile
• [ ] Grid goes from 3/4 columns to 2 and then 1 on mobile
• [ ] Text sizes adjusted for mobile
• [ ] Floating CTA does not block content
9.6 Functionality check
• [ ] Hamburger menu opens and closes properly
• [ ] FAQ Accordion works
• [ ] Back-to-top button appears and works
• [ ] Counters work with animation
• [ ] Fade-in animations work on scroll
• [ ] Header changes style on scroll
• [ ] FAQ search filters in real time (if present)
9.7 Performance check
• [ ] CSS and JS minified (.min.css / .min.js)
• [ ] Critical CSS in an inline <style> in the head of every page
• [ ] JavaScript with defer
• [ ] Icons as inline SVG
• [ ] Scroll listeners with passive: true
• [ ] No JavaScript errors in the console
9.8 Technical files check
• [ ] sitemap.xml: all pages exist and the URLs match
• [ ] robots.txt: valid and points to the sitemap
• [ ] manifest.json: valid
• [ ] favicon displays in the tab
9.9 Final report
When the check is done, show the user a summary report:
===== Final QA report =====
📊 Total pages: [number]
🔗 Valid links: [number]
❌ Broken links: [number]
🔗 External links: [number] (structure checked, not)
📝 Meta Tags:
- Unique title: ✅/❌
- Unique description: ✅/❌
- Canonical: ✅/❌
- OG Tags: ✅/❌
📐 Schema:
- WebSite: ✅/❌
- Organization: ✅/❌
- BreadcrumbList: ✅/❌
- FAQPage: ✅/❌
- Article: ✅/❌
🎨 Design:
- RTL: ✅/❌
- Responsiveness: ✅/❌
- Floating CTA: ✅/❌
⚡ Performance:
- CSS/JS minified: ✅/❌
- Critical CSS inline: ✅/❌
- Console errors: ✅/❌
📁 Technical files:
- sitemap.xml: ✅/❌
- robots.txt: ✅/❌
- manifest.json: ✅/❌
- favicon: ✅/❌
🚀 The site is ready to upload to the server!
Report to the user: "QA check complete. Here is the report: [report]. The site is ready to upload!"
Iron rules: always follow them
• A single H1 on every page, never two
• Unique content: no copy-paste between pages, including city pages
• Every link must work: check before moving on
• Schema on every page: at least BreadcrumbList on internal pages
• Unique meta tags: a different title + description on every page
• RTL: always dir="rtl" and lang="he" (unless the site is in English)
• Responsiveness: every page must work on Desktop, Tablet, Mobile
• Performance: CSS/JS minified, Critical CSS inline, defer on JS
• Don't build everything at once: step by step, with a check after each step
• Report to the user: at the end of each step, give a summary and wait for approvalOur team runs these processes on client sites every week as part of our organic SEO services. We'll start with a review of your site.
Last updated: October 14, 2026 · Written by the DigiAssets team