Descubra as top 30 bibliotecas de prompts e componentes 3D copy-paste.

sitesanimados.vibepreview.com

Prompt Mestre Exclusivo para Comunidade

#PROMTP########
You are acting as my Website Architect. Do NOT generate any website content yet. Your first job is to interview me to gather the inputs you need, then YOU will design the SEO/GEO strategy, sitemap, and content architecture yourself — I will not hand you keywords, I want you to derive them from my answers.

────────────────────────

STEP 0 — DISCOVERY INTERVIEW

────────────────────────

Ask me the following questions, one at a time (or grouped in small logical sets of 2-3 if that flows better), waiting for my answer before continuing. Do not skip ahead to building anything until all answers are collected and I confirm they're correct:

1. What's your business name?

2. What services or products do you offer? (be as specific as possible — I'll use this to define your core service pages)

3. Who do you serve? (your ideal customer/client)

4. What's your address, service area, or region? (city, multiple cities, state, or "fully online / nationwide")

5. What's the main goal of the site? Choose one or more: (a) Generate leads, (b) Book calls/appointments, (c) Showcase portfolio/work, (d) Sell products/services directly, (e) All of the above

6. What brand tone fits you best? (e.g. trustworthy & corporate, premium & modern, friendly & approachable, technical & authoritative, bold & disruptive — or describe your own)

7. What's your domain? (or "not registered yet" if you don't have one)

8. What are the 3 main topics/questions your customers most often ask about, or the 3 subjects most central to your service? (I will turn these into 3 published blog posts — give me real topics, not placeholders)

Once I've answered everything, summarize my answers back to me in a short recap and ask me to confirm before moving to Step 1.

────────────────────────

STEP 1 — YOU DERIVE THE SEO + GEO STRATEGY (do not ask me for this)

────────────────────────

Based only on my answers above, you will now generate, without asking me:

- 3-5 primary SEO keywords (high-intent, directly tied to my core service + location if local)

- 5-8 secondary/long-tail keywords (question-based and specific, the kind people type into AI assistants and voice search)

- A one-paragraph GEO entity summary: a clean, quotable 2-3 sentence description of the business (name, category, specialty, location, differentiator) written so it could be lifted verbatim by an AI answer engine

- The 3 blog topics from question 8, each rewritten as an SEO/GEO-friendly title (question-format where natural, e.g. "How Much Does [Service] Cost in [Region]?")

Present this strategy to me as a short summary before building anything, so I can sanity-check it.

────────────────────────

STEP 2 — SITE ARCHITECTURE & SITEMAP

────────────────────────

Once the strategy above is confirmed, output a full sitemap tree:

/ (Home)

/about

/services

/services/[service-1]

/services/[service-2]

/listings (portfolio/products/properties) — only include if goal includes showcase/sell

/listings/[item-detail-page]

/blog

/blog/[post-1-slug]

/blog/[post-2-slug]

/blog/[post-3-slug]

/contact

/legal (privacy-policy, terms) — no-index, still linked in footer

Rules:

- Every page reachable in 3 clicks or fewer from Home.

- Clean, descriptive URL slugs everywhere (no /page?id=12).

- Generate sitemap.xml (all pages, priority + change-frequency) and robots.txt (block /admin, /thank-you, duplicate/parameterized URLs).

- Breadcrumbs on every page except Home, marked up with BreadcrumbList schema.

- If goal = "book calls," the Contact page and every service page must include a booking-style CTA (not just a contact form) — mention this explicitly in each CTA's copy.

- If goal = "sell," Listings/Services pages need pricing or a clear "Buy/Start" CTA, not just "Learn more."

────────────────────────

STEP 3 — PAGE & SECTION STRUCTURE (semantic hierarchy)

────────────────────────

- Exactly ONE H1 per page, containing that page's primary or secondary keyword naturally.

- H2s divide major sections in logical order; H3s divide sub-points. Never skip a level.

- Standard page flow unless the page type demands otherwise:

1. Hero (H1 + subheadline + primary CTA matching the site's main goal)

2. Trust/proof strip (logos, review score, stats)

3. Core value/benefits (H2)

4. Explanation / how it works (H2)

5. Social proof (testimonials, case studies)

6. Secondary CTA or lead magnet

7. FAQ block (H2 "Frequently Asked Questions" + H3 per question) — required on Home, Services, and Listings detail pages

8. Final CTA

- Every section gets an anchor id (#services, #faq) for internal linking.

────────────────────────

STEP 4 — BLOG (3 posts, written and "published")

────────────────────────

Build a /blog index page (grid of post cards: title, excerpt, image, date, read-more link) plus 3 full blog post pages, one per topic from Step 1, each following this structure:

- H1 = the SEO/GEO-optimized title

- A direct 2-3 sentence answer to the core question in the first paragraph (GEO/AEO front-loading — this is the part most likely to get quoted by an AI or shown as a snippet)

- 3-5 H2 sub-sections expanding on the topic with real, useful detail (not filler)

- At least one structured element per post: a numbered list, comparison table, or short FAQ (H3s) with FAQPage schema

- A closing CTA linking back to the relevant service page

- Author byline, publish date, and estimated read time

- Meta title, meta description, and Article/BlogPosting schema (JSON-LD) per post

- Internal links: each post links to at least 1 service page, and each service page links to at least 1 relevant post

Mark all 3 posts as published (not drafts) with today's date, and add them to the sitemap and blog index.

────────────────────────

STEP 5 — SEO REQUIREMENTS

────────────────────────

- Unique <title> per page: [Primary/Secondary Keyword] + [Business Name], under 60 characters.

- Unique meta description per page, under 155 characters, keyword + benefit-driven.

- Semantic HTML5 (header, nav, main, section, article, footer).

- Canonical tag on every page.

- Internal links with descriptive anchor text (never "click here").

- Open Graph + Twitter Card tags per page (og:title, og:description, og:image, og:url).

- Fast-loading structure: no render-blocking inline styles, lazy-load below-the-fold images.

────────────────────────

STEP 5.5 — LAYOUT, GRID & RESPONSIVE RULES

────────────────────────

CONTAINER & WIDTHS:

- Max content width: 1200px, centered (margin: 0 auto), on ALL pages and sections.

- Full-width backgrounds are allowed (hero, CTA strips, footer), but the inner

content inside them must still be constrained to the 1200px container.

- Blog post body text: narrower reading column of 720-760px max, centered,

for readability (~65-75 characters per line).

- Never let text, images, or cards touch the edge of the viewport.

BREAKPOINTS (mobile-first):

- Mobile: up to 767px — single column, stacked sections.

- Tablet: 768px to 1023px — 2 columns max for cards/grids.

- Desktop: 1024px and up — full layout, container capped at 1200px.

SIDE PADDING (safe margins inside the container):

- Mobile: 16-20px left/right.

- Tablet: 32px left/right.

- Desktop: 40px left/right (until viewport exceeds 1280px, then the

1200px cap takes over).

VERTICAL SPACING:

- Section padding (top/bottom): 80-120px on desktop, 48-64px on mobile.

- Consistent spacing scale (8px base): 8 / 16 / 24 / 32 / 48 / 64 / 96.

- Gap between grid cards: 24-32px desktop, 16px mobile.

- Never stack two sections with the same background color without a

visual separator or clear spacing.

GRIDS & ELEMENT POSITIONING:

- Services/listings/blog cards: 3 columns desktop, 2 tablet, 1 mobile.

- Hero: text + CTA left, image/visual right on desktop (or centered if

no image); fully stacked on mobile with text first, image second.

- Testimonials: 2-3 columns desktop, horizontal swipe or stacked on mobile.

- FAQ: single column, full container width, accordion style.

- Footer: 3-4 columns desktop, stacked single column on mobile.

- Preserve the section ORDER defined in Step 3 on every breakpoint —

responsive behavior may stack elements, never reorder sections.

RESPONSIVE BEHAVIOR:

- Mobile navigation: hamburger menu; primary CTA button stays visible

in the header on all breakpoints.

- Tap targets on mobile: minimum 44x44px; buttons full-width on mobile

when inside forms or CTA blocks.

- Base font size: 16px minimum on mobile (never smaller for body text).

- Fluid typography: H1 ~40-56px desktop scaling down to ~28-32px mobile;

scale H2/H3 proportionally. Use clamp() where supported.

- Images: max-width: 100%, height: auto, with fixed aspect-ratio boxes

to prevent layout shift (CLS).

- No horizontal scroll on any breakpoint, ever.

- Sticky header allowed, max ~72px tall on desktop, ~60px on mobile.

────────────────────────

STEP 6 — GEO REQUIREMENTS

────────────────────────

- Open every major section with a direct, self-contained factual statement before elaborating.

- State who the business is, what it does, and where, together at least once near the top of Home/About (entity clarity).

- Use structured facts (lists, defined terms, numbers, comparisons) instead of long unstructured paragraphs.

- Pair persuasive copy with at least one concrete, citable fact per section (a number, a step, a guarantee, a credential).

- Reuse the GEO entity summary from Step 1 as a standalone "About [Business Name]" block that could be quoted out of context.

────────────────────────

STEP 7 — AEO REQUIREMENTS

────────────────────────

- FAQ H3s phrased as real questions, each followed immediately by a direct 40-60 word answer, then supporting detail.

- FAQPage schema (JSON-LD) on every FAQ block.

- Processes formatted as numbered lists (HowTo-style), not paragraphs.

- Organization/LocalBusiness schema in the footer of every page; Service schema on each service page; Article/BlogPosting schema on each blog post.

- One clear, quotable "what is [service]" definition sentence near the top of any page targeting a definitional keyword.

────────────────────────

STEP 8 — IMAGE & LOGO ORGANIZATION (apply automatically once assets exist)

────────────────────────

When I upload or reference real photos/logos, organize and name them automatically — don't ask me each time:

- /logo/logo-full-color.svg (header)

- /logo/logo-white.svg (dark backgrounds, footer)

- /logo/favicon.ico + /logo/favicon-512.png

- /images/hero/[page-slug]-hero.jpg

- /images/services/[service-slug]-01.jpg, -02.jpg

- /images/listings/[item-slug]-01.jpg

- /images/blog/[post-slug]-cover.jpg

- /images/team/[first-name]-[last-name].jpg

- /images/og/[page-slug]-og.jpg (1200x630)

Rules:

- Alt text formula: "[What's in the image] — [Business Name/Service context]," never generic filenames.

- Full-color logo in header, white/inverted version in footer if the footer background is dark; favicon generated from the icon-only mark if one exists.

- Serve images at the size actually displayed; use responsive srcset where supported.

- ImageObject schema on the primary image of each service/listing/blog page.

- If an asset is missing when building a page, use a clearly labeled placeholder in the exact final dimensions/position so swapping later doesn't shift the layout.

────────────────────────

STEP 9 — FINAL OUTPUT ORDER

────────────────────────

1. Ask the Step 0 questions.

2. Confirm my answers back to me.

3. Present the Step 1 SEO/GEO strategy for approval.

4. Present the Step 2 sitemap for approval.

5. Only then build the full site: all core pages + blog index + 3 published posts, following every rule above.