SEO builder
Build SEO prompts around intent, structure, and E-E-A-T
Use category-specific controls for articles, service pages, and FAQ content. The dedicated SSR route helps attract organic traffic and acts as an SEO landing page itself.
jsonpromptbuilder.com
Server assembly
Organic
SEO
Create an SEO article about choosing a CRM for a small business. Include structure, FAQ, and a clear CTA.
- Common fields + category settings + humanization
{
"category": "seo",
"task": "...",
"common_settings": { ... },
"category_settings": { ... }
}Builder
Builder: SEO
Start with the common settings, then tune the category-specific fields and generate a ready-to-use JSON prompt.
Builder mode
Builder mode
Play mode keeps the whole form on one screen, while Wizard guides the user through clear numbered steps.
Blank mode
Start from scratch
Use it when the request does not fit one category cleanly and you want a more universal JSON prompt setup.
PRO
Quick start and presets
Use a built-in scenario to fill the form fast, then export, import, or share your own preset configuration.
Preset families
Core starters
Reliable starting points for the most common use cases in this category.
Local SEO FAQ page
Built for local intent, user questions, and stronger E-E-A-T signals.
Use case: General use case
SEO traffic article
For a detailed article aimed at informational intent and keyword-cluster coverage.
Use case: General use case
Service page for leads
A starting point for a service landing page with commercial intent and a lead CTA.
Use case: General use case
Preset families
Competitor analysis
Scenarios built around market comparison, objection handling, and differentiation.
SEO competitor gap article
For articles that compare the market, address objections, and expose what alternatives are missing.
Use case: Competitor gap analysis
Preset families
Product comparison
Templates for comparison intent, side-by-side evaluation, and option selection.
SEO product comparison article
Built for comparison SERPs where a table, decision criteria, and balanced evaluation matter.
Use case: Product comparison intent
1
Task
Describe the plain-language request in your own words. This value will be stored as the task field in the final JSON.
Main task
Describe the plain-language request in your own words. This value will be stored as the task field in the final JSON.
2
Common settings
These parameters affect the result regardless of the selected category.
Target audience
Who the content or prompt is primarily written for.
Beginners: an audience with limited experience that needs a clear explanation.
Reasoning method
How the model should approach the task before producing the final output.
Standard: a direct answer without an extra reasoning framework.
Output language
Which language the model should use in the generated result.
English: the output should be written in English.
Content length
How concise or detailed the final output should be.
Tone
How the final output should sound emotionally.
Friendly: warm, light, and easy to understand.
Writing style
How the final output should be organized and presented.
Concise: minimal fluff and maximum substance.
Output format
In what format the model should return the result.
HTML: the result should be returned in HTML.
3
Category-specific settings
These fields depend on the selected category and its use case.
SEO brief
Baseline page, intent, role, and SEO objective settings.
Writer role
What professional role the model should take.
SEO copywriter: writes with focus on rankings and organic traffic.
What to create
What type of SEO content should be created.
SEO article: a full article designed for search visibility.
Page type
What page the text will be placed on.
Blog article: best for informational traffic.
SEO goal
What main result the content should deliver.
Reach top 10: focus on search positions.
Search intent
What the user wants to get from the query.
Informational: the user wants an explanation or answer.
Industry
What industry the site or business belongs to.
Health: topics around medicine, wellness, and self-care.
Target region
What market or geography the text targets.
Global: content without strong country-specific focus.
Semantic core
Primary keyword, supporting queries, and semantic usage rules.
Keyword strategy
How keywords should be woven into the text.
Natural: keywords are integrated smoothly without overload.
Primary keyword
The main search phrase the article should be built around.
PRO
Semantic and long-tail assistant
A PRO helper that expands the primary keyword into synonyms, LSI terms, and triplets. Enabled suggestions are appended automatically during JSON generation and preset export.
Secondary keywords
List secondary search queries the article should also cover. Use one per line.
LSI and semantic terms
Topical terms and entities that make the article semantically richer. Use one per line.
Triplets and long-tail phrases
Longer search phrases with 3+ words that can be distributed across headings and paragraphs. Use one phrase per line.
Forbidden keywords
Words, brands, or phrases the article must avoid. Use one per line.
Exact match policy
How strictly the primary keyword should appear in exact form.
Sparse exact matches: use the primary keyword precisely but rarely.
Technical SEO structure
Controls heading depth, tables, lists, and keyword-density limits.
Heading structure
How H1, H2, and H3 should be organized.
Classic H1-H2-H3: a standard and clear SEO structure.
H2 count
How many main H2 sections the article should contain.
H3 per H2
How deeply each main section should be developed with H3 subsections.
Allow H4
Enable this when the article may use deeper nested headings.
Avoid H2-only structure
Pushes the model to avoid a flat H2-only outline.
Include lists
Requires bullet or numbered lists where they improve readability.
Include comparison table
Requests at least one table for comparison or structured overview.
Table purpose
What job the table should perform inside the article.
Option comparison: helps the reader choose between several options.
Keyword density limit
An upper limit for repeating the primary keyword to avoid stuffing.
Up to 1.0%: very restrained keyword usage.
Internal links
How many internal links should be planned.
External links
How many external source links or references to include.
Meta tags and snippet
Title and meta description requirements for SERP appearance and click-through.
Meta description style
What tone and format the search snippet should have.
Benefit-based: immediately shows the reader's benefit.
Generate title tag
Adds an explicit requirement to generate the page title tag.
Generate meta description
Asks the model to produce a dedicated meta description for the search snippet.
Title max length
What maximum character limit to set for the title tag.
Meta description max length
What character limit to set for the meta description.
Require primary keyword in title
Makes the primary keyword mandatory inside the title tag.
Require primary keyword in description
Makes the primary keyword mandatory inside the meta description.
Readability and rhythm
Sets the opening hook, reading level, and sentence rhythm. The humanization block above removes extra AI markers.
Intro hook style
How the opening lines should grab attention.
Question hook: open with a question that reflects the reader's pain or curiosity.
Reading level
How simple or advanced the article language should feel.
Very simple: short sentences and minimal jargon.
Sentence rhythm
How much the text should vary sentence length to feel more alive.
Prefer active voice
Keeps the copy more direct and energetic by favoring active voice.
Avoid filler openers
Avoids generic paragraph openings and empty introductory phrasing.
E-E-A-T and experience signals
Defines how the article should feel experienced, reliable, and authoritative.
E-E-A-T level
How strongly the text should show experience and expertise.
Basic: a clean and useful text is enough.
Experience signal mode
How the article should signal experience and real familiarity with the topic.
First-hand experience: the copy should feel like it comes from direct practical work.
Authority signals
What proof formats should be included to make the article feel more authoritative.
You can choose multiple options.
Evidence style
What kind of supporting evidence should dominate the article.
Facts and data: prioritizes numbers, research, and verifiable claims.
Engagement and conversion
Summary, FAQ logic, internal-link guidance, and the final CTA.
FAQ block
Whether the text should include a dedicated FAQ block.
No FAQ: the text has no dedicated question block.
FAQ source
What source should shape the FAQ block.
People Also Ask: base the FAQ on common SERP questions.
Include TL;DR
Requests a short summary block for quick scanning.
TL;DR position
Where the short summary should appear inside the article.
At the top: place the summary before the main article.
Internal link targets
Which pages, topics, or URLs should be linked from this article. Use one per line.
Anchor style
How the anchor text for internal links should be phrased.
Natural anchors: links flow smoothly as part of the sentence.
Call to action
What the reader should do after reading.
Soft CTA: invite the reader to learn more or keep browsing.
4
Additional sections
Named blocks for rules, constraints, examples, and any context that does not fit into the standard fields.
Additional sections
Named blocks for rules, constraints, examples, and any context that does not fit into the standard fields.
Sections left: 10
Use this area for brand rules, negative examples, legal constraints, or formatting instructions.
5
Humanization controls
Reduces recognizable AI markers, makes the tone feel more natural, and lets you explicitly exclude common AI phrases.
Humanization controls
Reduces recognizable AI markers, makes the tone feel more natural, and lets you explicitly exclude common AI phrases.
Which AI markers to avoid
Choose the phrases and constructions the model should avoid.
Custom phrases to exclude
List additional phrases or constructions to avoid. Use one phrase per line.
6
Review and generate
Use the generated JSON prompt right away: copy it, download it, and drop it into any AI workflow or internal tool.
Result
Generated JSON prompt
Use the generated JSON prompt right away: copy it, download it, and drop it into any AI workflow or internal tool.
Organic
SEO
The SEO builder is designed for informational, commercial, and service pages. It helps you create not just a prompt, but a structure that is clear both to the editor and to the model.
You can define search intent, page type, industry, region, keyword strategy, E-E-A-T level, FAQ usage, meta description style, and internal linking requirements.
This approach is especially useful for content teams, agencies, and site owners who want an SEO workflow that is repeatable and scalable.
FAQ
FAQ
Why does the SEO builder have its own page?
A dedicated slug gives the category its own SEO relevance, metadata, FAQ, and long-form content that can rank as a landing page.
Does the builder support search intent and E-E-A-T?
Yes. The SEO category includes dedicated controls for intent, structure, industry, geography, and expertise signals.
Can I use it for both articles and service pages?
Yes. The category includes page type and SEO goal controls, so it works across multiple SEO use cases.
Will the raw SEO config be visible in the browser?
No. The full logic stays on the server, while the client receives only the data required to render the current form and the final result.