How to Write an AI Website Brief for WordPress
A request such as “build a modern website” leaves almost every important decision open. Who is the page for? Which action matters? Can the agent change the navigation? Where should the product claims come from? A useful AI website brief answers those questions before the first page is written. This guide focuses on briefing an […]
A request such as “build a modern website” leaves almost every important decision open. Who is the page for? Which action matters? Can the agent change the navigation? Where should the product claims come from? A useful AI website brief answers those questions before the first page is written.
This guide focuses on briefing an agent for an existing WordPress site using Shilpi. The sample business below is fictional; replace its details with your own approved information before using the prompt.
1. Define one audience and one primary action
Start with the visitor’s problem, then describe the action that would help them move forward. “Small design studios comparing a WordPress workflow” is more useful than “everyone who needs a website.” “Read the setup guide” is more concrete than “increase engagement.”
Give each page a primary purpose. A homepage may introduce the product, a tutorial may help someone finish a task, and a pricing page may explain available plans. They can support the same business goal without repeating the same copy.
2. Separate confirmed content from missing information
Provide approved service descriptions, product facts, contact details and brand assets. Label anything uncertain. If pricing is unavailable, ask the agent to omit it or leave a clearly identified draft note. Do the same for customer logos, testimonials, awards and performance figures.
Tell the agent where it may verify product details. For a Shilpi build, link to the documentation and relevant existing pages. A visual reference can guide layout; it should not become a source for your business claims.
3. Describe the existing site before proposing changes
On an established website, the brief should ask the agent to inspect pages, templates, navigation and design variables before writing. Shilpi’s MCP tools can identify existing records by ID or slug, which makes an update target explicit.
Specify the page to create or revise, and whether the work should remain a draft or be published. If the task concerns one landing page, say which shared elements it should reuse. A clear boundary makes the result easier to review.
4. Turn visual preferences into decisions
Replace “premium and clean” with observable choices: a restrained colour palette, readable body text, generous spacing and one prominent primary button. Include the assets to use and describe how the page should behave on smaller screens.
Shilpi separates body HTML from Page CSS and JavaScript. Ask the agent to reuse existing design variables and put any new page-specific styling in that page’s CSS. This keeps a new landing page connected to the existing site design. Read the design tokens guide for the underlying approach.
5. Use this example brief
Create a draft landing page for a fictional studio called Northline. The audience is small businesses planning their first brand website. The primary action is to visit our existing contact page.
First inspect the current WordPress pages, header, footer and design variables. Use the slug northline-website-service and update that record if it already exists. Reuse the existing header and footer.
Include a clear service introduction, the problems the service addresses, a three-step process, a list of deliverables and answers to common scope questions. Use only the service details I supply. Omit prices, testimonials and customer logos until I provide approved material.
Use semantic body-only HTML, the site’s existing colours and typography, and Page CSS for any new styling. Keep the layout readable on desktop, tablet and mobile. Use descriptive links and a logical heading order.
Save as a draft. Read the saved record back, inspect the preview, check links and report any missing content. Return the preview URL and a short list of changes.
Replace the fictional name, slug and scope before sending this to an agent. Then attach your approved service information. The example deliberately routes enquiries to an existing page, so it does not imply that a new form or delivery workflow has been configured.
6. Give focused revision requests
Once a draft exists, describe the specific problem. “Reduce the introduction to two sentences and move the process section above the deliverables” gives the agent a concrete edit. “Make it better” invites another round of guessing.
Review content, layout and behaviour separately. First check whether the offer is accurate. Then inspect hierarchy and spacing. Finally follow links and test interactive elements. The launch checklist provides a structured final pass.
Frequently asked questions
How long should an AI website brief be?
Long enough to resolve the decisions that affect the page. A focused page may need only a few paragraphs; a full site needs page-level goals, a content inventory and shared design rules.
Can I use the same brief for a redesign?
Yes, but name the existing pages and the elements that should be retained. Explain which problem the redesign needs to solve, and identify any URLs that must remain stable.
Where should I start?
Use Shilpi’s website prompt builder to organise your requirements, then add the approved content and the exact scope of the first task. For the connection and build process, follow the AI and MCP workflow guide.
