Step 1 — Project
Brand name
The name of your company, product, or brand. It will be used consistently in the generated SEO prompt and meta tags.
- Example
- Acme Inc, My SaaS, DevHire
- Default
- (empty — prompt will use a placeholder)
Domain
Your website’s full URL. Use HTTPS and no trailing slash. This is used for canonical URLs, sitemaps, and Open Graph tags.
- Example
- https://example.com, https://myapp.io
- Default
- (empty — prompt will use a placeholder)
Project description
A short description of what your project or site does. Helps the SEO prompt understand context and suggest relevant structure.
- Example
- A platform to hire developers from GitHub
- Default
- (empty)
Page type
The kind of page or site you’re optimizing. This shapes the content structure and SEO recommendations.
- Example
- SaaS Landing Page, Blog, E-commerce
- Default
- SaaS Landing Page
- Options
- SaaS Landing Page · Blog / Content Site · Portfolio / Personal Brand · E-commerce · Full Web App · Documentation Site
Tech stack
The framework and technologies your site uses. The prompt will suggest implementation details that match your stack (e.g. Next.js metadata API).
- Default
- Next.js (App Router) + TypeScript + Tailwind + MongoDB
- Options
- Next.js (App Router) + TypeScript + Tailwind + MongoDB · Next.js (Pages Router) + TypeScript · React + Vite + TypeScript · Remix + TypeScript · SvelteKit · plain HTML / CSS / JS · custom
Custom stack
Only shown when Tech stack is “Custom”. Describe your stack in your own words (e.g. Laravel + React, WordPress).
- Example
- Laravel + React, WordPress + custom theme
Step 2 — Keywords
Primary keyword
The main search phrase you want this page to rank for. One primary keyword per page is recommended to avoid cannibalization.
- Example
- best project management tool for startups
- Default
- (empty)
Secondary keywords
Related or supporting keywords (LSI, long-tail). Add them as tags; they’ll be woven into the content and headings.
- Example
- remote developer hiring, GitHub talent, find developers
- Default
- (empty)
Search intent
What the user is trying to do when they search: learn (informational), evaluate/buy (commercial), take action (transactional), or find a brand (navigational).
- Default
- Commercial (user wants to evaluate / buy)
- Options
- Commercial · Informational · Transactional · Navigational
Target audience
Who you’re writing for. Helps tailor tone, depth, and calls-to-action in the prompt.
- Example
- CTOs, HR leaders, indie hackers, small business owners
- Default
- (empty)
Step 3 — Content
Competitor domains
Sites you consider competitors. The prompt can reference analyzing and outperforming them (e.g. for content ideas).
- Example
- competitor.com, other-tool.com
- Default
- (empty)
Content style
The overall style of your content: professional, casual, technical, or marketing-focused.
- Default
- Professional / Enterprise
- Options
- Professional / Enterprise · Casual / Conversational · Technical / Developer-focused · Marketing / Sales-driven
Tone of writing
The voice of your copy: authoritative, friendly, persuasive, educational, or minimalist.
- Default
- Authoritative
- Options
- Authoritative · Friendly · Persuasive · Educational · Minimalist
Content length
Target length for the main content. Affects how much the prompt asks for (e.g. short vs long-form).
- Default
- Medium (1000–1500 words)
- Options
- Short (500–800 words) · Medium (1000–1500 words) · Long-form (2000–3000 words) · Comprehensive (3000+ words)
Extra notes
Any special requirements: accessibility, specific schema, regional SEO, or custom instructions for the AI.
- Example
- Focus on EU audience, add FAQ schema, WCAG AA
Step 4 — Technical
Title format
How the page title (and similar titles) should be structured: brand first, keyword first, or combined.
- Default
- Brand | Keyword
- Options
- Brand | Keyword · Keyword — Brand · Keyword | Brand · Brand: Keyword
Rendering strategy
How your app serves pages: static (SSG), server-rendered (SSR), incremental (ISR), or client-side (CSR). Affects SEO and performance advice.
- Default
- SSG (Static Site Generation) for max performance
- Options
- SSG (Static Site Generation) for max performance · SSR (Server-Side Rendering) for dynamic pages · ISR (Incremental Static Regeneration) · CSR (Client-Side Rendering) — SEO limited
Structured data
Which JSON-LD schema(s) to include: WebSite, Organization, Article, Product, FAQ, or none.
- Default
- WebSite + SoftwareApplication schema
- Options
- WebSite + SoftwareApplication schema · WebSite + Organization schema · Article + BreadcrumbList schema · Product + Review schema · FAQPage schema · none
Sitemap
How the sitemap is generated: dynamic route, static file, or a package like next-sitemap.
- Default
- dynamic XML sitemap via /sitemap.xml route
- Options
- dynamic XML sitemap via /sitemap.xml route · static sitemap.xml in /public · next-sitemap package
Image format
Preferred image format and optimization (e.g. WebP, AVIF, next/image).
- Default
- WebP with AVIF fallback
- Options
- WebP with AVIF fallback · AVIF primary · next/image with automatic optimization
Load target
Target load time for performance (e.g. under 2s). Used in the prompt’s performance section.
- Default
- under 2s (good)
- Options
- under 1.5s (excellent) · under 2s (good) · under 3s (acceptable)
CDN
Content delivery network you use or plan to use. Referenced in performance and caching advice.
- Default
- Vercel Edge Network
- Options
- Vercel Edge Network · Cloudflare · AWS CloudFront · none / not decided
Analytics
Analytics or tracking setup (e.g. GA4, Plausible, Vercel Analytics). The prompt can mention integration.
- Default
- Google Analytics 4 + Google Search Console
- Options
- Google Analytics 4 + Google Search Console · Plausible Analytics (privacy-first) · Vercel Analytics · PostHog · none
Robots.txt rules
Custom rules for robots.txt (e.g. disallow /api/, /admin/). Leave blank for a sensible default.
- Example
- block /api/ and /admin/, allow all public pages
Payment & delivery
What it costs
$9 once, per prompt. There is no account, no subscription, and nothing recurring to cancel.
How you receive it
The prompt appears on the receipt page the moment payment is confirmed, and an email arrives with a PDF and a Markdown copy attached.
Re-downloading later
Your receipt links to a permanent delivery page. Open it any time to copy the prompt, download it again in any format, or resend the email.
If the email never arrives
Check spam first, then use the resend button on your delivery page. If you were charged and cannot find the order at all, email support with your payment ID.
- Example
- support@seopromptai.com
If a payment fails
Nothing is charged and your draft stays in this browser, so you can retry checkout without re-entering anything.
Still stuck?
Email support@seopromptai.com and we will get back to you.