What is foundation SEO?

Foundation SEO is the base layer of technical and on-page signals that tell search engines what each page is called, what it's about, and which URL is the canonical one. It covers titles and meta descriptions, a clean heading structure, Open Graph and Twitter share previews, robots.txt and your sitemap, canonical tags, light structured data, and alt text. Get this layer right before investing in content and links — otherwise even great content underperforms.

What should a page title and meta description look like?

Keep the title near 50 to 60 characters and the description near 150 to 160 so neither truncates in search results. Lead with a clear benefit, write for a human rather than stuffing keywords, and give every important page — home, pricing, product — a unique title and description. Duplicates blur which page should rank.

Why do Open Graph tags matter?

Open Graph tags decide what people see when your link is pasted into Slack, X, or any app that unfurls links — the title, description, image, and URL. A blank or broken preview is a missed click. Use a 1200×630 image and set twitter:card to summary_large_image so X renders the large preview instead of a small thumbnail.

Does structured data help with AI search?

Yes. JSON-LD schema labels what kind of thing a page is — Organization, Article, FAQPage, SoftwareApplication — in language machines can't misread. Clean entities help AI answer engines like ChatGPT and Perplexity cite you more confidently, because the page and its schema agree on who you are. Pages with multiple relevant schema types are measurably more likely to be cited.

What tools can I use to verify my SEO?

Google Search Console lets you verify the site, submit your sitemap, and watch indexing and queries. Ahrefs gives a professional-grade pass across content, social tags, indexability, structured data, and images. Free auditors like TrustSEO run a check on any live URL and can generate tuned fixes. Validate schema with Google's Rich Results Test.

What Matters in Foundation SEO

Before a single backlink or blog post can do its job, a page has to answer three quiet questions for Google—and for every app that unfurls a link, from Slack to X: What is this page called? What is it about? Which URL is the real one? Foundation SEO is the layer that answers them. Get it wrong and even great content underperforms; get it right and everything you build on top compounds.

This is the short version—the handful of things that actually matter, with no busywork. Each section closes with a copy-paste prompt you can hand to your AI editor. Swap YOUR_SITE_URL for your live domain before you send it.

What matters in foundation SEO

1. Page title and meta description

This is the line and snippet a searcher reads before deciding whether to click—your first and often only pitch in the results.

Keep the title near 50–60 characters and the description near 150–160, so neither truncates mid-thought.
Lead with the benefit, write for a human, and skip the keyword stuffing.
Give every important page—home, pricing, product—a unique title and description. Duplicates blur which page should rank.

Implementation prompt

# SEO fix: Title & meta description — YOUR_SITE_URL

I am improving foundation SEO on https://YOUR_SITE_URL. The stack is Next.js.

Please help me:
- Set a unique page title and meta description for each main route (home, pricing, key marketing pages).
- Keep titles around 50–60 characters and meta descriptions around 150–160 characters where sensible.
- Remove duplicate or empty metadata.

Use Next.js conventions (App Router: generateMetadata in route .tsx files, or the metadata export). Fix issues in priority order (homepage and money pages first).

Detected stack: Next.js — prefer .tsx and app/ or pages/ patterns.

2. One H1 and heading order

Headings are the page's outline. Google reads that outline to understand structure, and so do screen readers.

Use exactly one H1, stating the topic in plain language.
Nest H2 and H3 in logical order—don't jump from H2 to H4 without reason.
A tangled heading tree shows up fast in Ahrefs → Content, so it's worth a quick check.

Implementation prompt

# SEO fix: Heading structure (H1–H3) — YOUR_SITE_URL

I am fixing heading hierarchy on https://YOUR_SITE_URL (Next.js).

Please:
- Ensure each page has exactly one H1 that matches user intent.
- Map H2/H3 to section structure; fix multiple H1s or wrong order.
- Suggest copy tweaks only if a heading is vague or duplicate.

Use stack-appropriate files (.tsx components, MDX if we use it). Prioritize high-traffic pages first.

Detected stack: Next.js.

3. Open Graph and X (Twitter) cards

The moment someone pastes your link into a chat or a tweet, Open Graph tags decide what they see—title, description, image, URL. A blank preview is a missed click.

Ship a 1200×630 image. No designer handy? Build one fast with the BruhGrow OG Generator.
Set twitter:card to summary_large_image so X renders the big, eye-catching preview instead of a thumbnail.

Implementation prompt

# SEO fix: Open Graph & Twitter/X cards — YOUR_SITE_URL

I need correct social previews for https://YOUR_SITE_URL (Next.js).

Please:
- Add or fix Open Graph tags: og:title, og:description, og:image (1200x630), og:url, og:type, og:site_name where applicable.
- Add Twitter/X meta: twitter:card = summary_large_image, plus title, description, and image.
- Ensure og:image URLs resolve on production (not localhost).

Use Next.js metadata API or head management. If we use dynamic OG images (e.g. /api/og), wire them per route where it helps.

Detected stack: Next.js — .tsx metadata or layout files.

4. robots.txt and XML sitemap

These two files tell crawlers where to go and where not to bother.

robots.txt flags what to skip and points to your sitemap—and it must reference your production host, never localhost.
Your sitemap lists the URLs you want found. Submit it in Google Search Console so discovery isn't left to chance.

Implementation prompt

# SEO fix: robots.txt & XML sitemap — YOUR_SITE_URL

I am fixing crawl signals for https://YOUR_SITE_URL (Next.js).

Please:
- Ensure robots.txt lives at the site root, uses the live domain, and references the sitemap URL(s).
- Confirm sitemap.xml (or generated sitemap) includes important public URLs and excludes private or duplicate junk.
- Remove any dev/staging URLs accidentally shipped to production config.

Use Next.js patterns (e.g. app/robots.ts, sitemap.ts, or static public files). Order fixes by crawl impact first.

Detected stack: Next.js.

5. Canonical URL and indexability

When the same content lives at more than one address, you choose the winner—or Google chooses for you.

A canonical tag names the preferred URL across duplicates (www vs. bare domain, query strings, and the like).
Watch for an accidental noindex on a live page or a 404 on a route that matters. Audits file both under indexability.

Implementation prompt

# SEO fix: Canonical URLs & indexability — YOUR_SITE_URL

I am fixing duplicate URL and indexing issues on https://YOUR_SITE_URL (Next.js).

Please:
- Add or fix canonical link tags so one preferred URL is clear per template.
- Search for accidental noindex, wrong robots meta, or blocking that should not apply to production.
- Flag redirect chains or soft 404s on key pages.

Use Next.js metadata and middleware only where appropriate. Prioritize homepage, product, and blog templates.

Detected stack: Next.js.

6. Structured data (JSON-LD) and AI search readiness

Schema is how you tell a machine what kind of thing a page is, in language it can't misread.

JSON-LD labels the page's type—Organization, WebSite, Article, FAQ, SoftwareApplication, and so on.
Clean entities help AI search (AEO) too: assistants like ChatGPT and Perplexity cite you more confidently when the page and its schema agree on who you are.
Validate with the Google Rich Results Test, and use Ahrefs → Structured data to see what crawlers actually parse.

Implementation prompt

# SEO fix: JSON-LD schema & AI Search Readiness (AEO) — YOUR_SITE_URL

I am improving structured data on https://YOUR_SITE_URL (Next.js).

Please:
- Add or refine JSON-LD for Organization, WebSite, and Article (for blog posts) as a sensible baseline.
- Include a section on AI Search Readiness (AEO): how clear entity definitions (JSON-LD) and semantic headings help LLMs like GPT-4 or Perplexity understand and cite the site.
- Keep markup valid; suggest testing with Google Rich Results Test.

Use Next.js (script tags in layout/page .tsx or a small component). Prioritize templates with the highest visibility.

Detected stack: Next.js — .tsx and JSON-LD in script type="application/ld+json".

7. Images and alt text

Alt text serves two audiences at once: people using screen readers, and image search.

Give meaningful images short, accurate alt text that describes what's in the frame.
Purely decorative images can carry empty alt—but never leave a hero image or key thumbnail undescribed.

Implementation prompt

# SEO fix: Image alt text & accessibility — YOUR_SITE_URL

I am fixing image SEO on https://YOUR_SITE_URL (Next.js).

Please:
- Audit Next/Image and img usage; add descriptive alt for content images; use empty alt only for decorative graphics.
- Fix icons or logos that carry meaning but currently have empty alt.
- Note any lazy-loading or LCP-sensitive images that need special handling.

Use .tsx components. Prioritize above-the-fold and template images first.

Detected stack: Next.js.

Tools that help you verify

Shipping is half the work; confirming it landed is the other half.

Google Search Console — Verify the site, submit the sitemap, and watch indexing and queries roll in.
Ahrefs — Paid, but its Content, Social tags, Indexability, Structured data, and Images reports give you a professional-grade pass.
TrustSEO — A free audit on any live URL. Its Implementation Prompt feature generates fixes like the ones above, tuned to your page's issues.

Implementation prompt — full foundation pass

# SEO Audit follow-up: Foundation fixes — YOUR_SITE_URL

I ran an SEO audit on https://YOUR_SITE_URL (Next.js). Help me fix issues in priority order, starting with the most impactful.

Include:
- Metadata (title, description), single H1 and heading order.
- Open Graph and Twitter large-image cards; production-safe image URLs.
- robots.txt, sitemap, canonicals, and indexability (noindex, status codes).
- JSON-LD baseline plus a short note on AI Search Readiness (AEO) and entity clarity.
- Image alt text for meaningful assets.

Detected stack: Next.js — use .tsx and framework conventions (App Router preferred).

Before you ship

A quick last look, top to bottom:

1–2: Titles, descriptions, and heading structure clean on every key page.
3: OG and X previews correct on production—lean on BruhGrow if you need images in a hurry.
4–5: robots and sitemap pointed at the live host, the sitemap submitted in Search Console, canonicals and indexability sane.
6–7: Light, validated schema; alt text on the images that matter.
Re-scan with TrustSEO or Ahrefs once it's all in place.

Nail this layer first. Then—and only then—pour your energy into content and links, where it'll actually pay off.

List your product on MarketingDB if you want a permanent indexed listing sitting on top of solid SEO basics.

What Matters in Foundation SEO

Key takeaways

What matters in foundation SEO

1. Page title and meta description

2. One H1 and heading order

3. Open Graph and X (Twitter) cards

4. robots.txt and XML sitemap

5. Canonical URL and indexability

6. Structured data (JSON-LD) and AI search readiness

7. Images and alt text

Tools that help you verify

Before you ship

Frequently asked questions

Get your startup discovered.

Related guides