AI Website Builder
SEOBlogy · automated site factory
● Pipeline live
Claude content + keywords GPT-4o fallback + DALL·E FLUX Replicate images Cloudinary image CDN GitHub Actions build engine Netlify hosting + functions
Generate a website
Fill the form → press Generate → download the ZIP right here
Building...
1
Trigger
2
AI content
+ images
3
Link
verify
4
ZIP
ready
⬇️ Download Website ZIP
Site mode
Landing page
1 page + sections
Single funnel page for Google Ads, sub-services shown as sections
~8–12 min
Hub mini-site
5–10 pages
Hub page plus a dedicated child page for every service
~12–18 min
Full website
20+ pages
Categories, service pages and about — AI builds the structure
~20–30 min
Topic Cluster
1 pillar + N pages
One topic, many problem pages — topical authority for local SEO
~15–25 min
pSEO Multi-City
NEW
1 service × N cities = N pages
Pulls business config + city list from Google Sheets — one city landing page per row, auto-shuffled sections, Claude-written content
~2–4 min per city · no manual input needed
Blog Engine
PRO
N topics = N ranking articles
Analyses the top-5 ranking pages for each topic, then writes an original, E-E-A-T article that beats them — SERP-informed, brand-voice, competitor-sanitized
~3–6 min per article
Business info required
Services — landing page
Ye service name nahi lagta
Auto mode: Leave sub-services empty — Claude will generate 6 relevant sub-services for this industry automatically.
Services — hub mini-site
Hub mode needs at least 1 service (ya SEO data URL do)
Hub mode: Every service gets a dedicated page, all linked inside the hub folder.
Services — full website
Full site needs at least 3 services
Full site: 10–20 services work best. AI organizes them into categories — every service gets its own SEO page.
Topic Cluster settings
Topic cluster mode needs at least one cluster
Skip pillar page
Generate only problem pages, no top-level pillar
Cluster format: Each line = one cluster. Use Cluster Name :: problem1, problem2, problem3. Each problem becomes a separate SEO page.
pSEO — area pages required
Site URL is required for pSEO mode
Give a plan URL, or open Advanced and supply the Google Sheets IDs instead
How it works: the plan's mode5_pseo.areas lists every area that has its OWN search demand — one page each, targeting that area's real Planner keywords. Claude writes the local profile (neighbourhoods, landmarks, transport, peak season) in one call per area, and coordinates come from OpenStreetMap, never from the model. Business details come from the Business info section above. Run the keyword tool with your CITY as the target location (not the country) so it returns that city's real sub-areas.
Google Sheets override (optional — only if you keep your data in sheets)
Supply BOTH ids to use sheets instead of the plan. Sheet rows always win over the plan + AI profile.
API key: set PSEO_SHEETS_API_KEY in the hosting env vars — never typed here.
Blog engine settings required
Blog engine needs at least 1 topic
How it works: For each topic we search its REAL primary keyword (from the plan), pull the top-5 ranking pages, and distil them into anonymised facts — brand names, phone numbers and marketing filler are stripped, only data-bearing lines (prices, ranges, standards, timeframes) survive. Those facts + the plan's keywords, PAA questions and must-mention entities go into BOTH the outline and every section, so the article beats the SERP instead of paraphrasing it. Output: E-E-A-T byline, FAQs, cross-linked articles and type-matched schema (HowTo / Article / FAQPage / ItemList + breadcrumbs). Set SERPAPI_API_KEY and SCRAPINGBEE_API_KEY in the builder's GitHub secrets — without them, articles still generate from the keyword + expertise.
Image & logo model
Replicate FLUX
Faster · recommended
GPT-Image-2
Higher quality · slower
Replicate FLUX
Fast · default
GPT-Image-2
Premium · slower
Social media links (optional)
Options
Internal links between pages
Service pages will link to each other
Dev.to backlinks
Publishes a Dev.to article for every service
Landing page
~8–12 min