// 03 Tiers
Grow ships agent-native marketing sites for AI startups, agent platforms, and developer tools — engineered so ChatGPT, Perplexity, Claude, and Google AI Overviews can cite your product accurately. We offer three productized engagements: Agent-Native Website Build, Agent Readability Audit, and Schema Optimization. Fixed price, fixed scope, 48-hour delivery on the launch tier.
Why this matters right now: 83% of AI Overview citations come from pages outside the organic top 10, 73% of sites are quietly excluded from AI citations by fixable technical issues, and pages over 20,000 characters receive 4.3× more AI citations than thin pages (Princeton GEO framework). The good news: every one of these is fixable.
· refreshed monthly
// Services
Agent-native web design agency.
Services
Contact
hello@grow.contactCustom-coded, LLM-readable
Semantic HTML, JSON-LD, llms.txt, OpenGraph, sitemap. Shipped in 48 hours with a fixed price and a written launch date.
View Build Specs →→$ agent-readability audit https://example.com
[OK] semantic HTML — 92/100
[WARN] missing JSON-LD Product schema
[OK] llms.txt found at root
[FAIL] OpenGraph image — 1200×630 required
[WARN] sitemap.xml missing lastmod
Score: 67/100 (needs work)Score + fix-list in minutes
Run your site through ChatGPT, Perplexity, Claude, and Google AI Overviews. Get a scored report with exact fixes.
Audit Your Site →→{
- "@type": "WebPage",
- "name": "Home"
+ "@type": "Product",
+ "name": "Nimbus Agents",
+ "offers": {
+ "@type": "Offer",
+ "price": "49.00",
+ "priceCurrency": "USD"
+ },
+ "aggregateRating": {
+ "@type": "AggregateRating",
+ "ratingValue": "4.8",
+ "reviewCount": "127"
+ }
}JSON-LD that agents trust
Upgrade generic WebPage markup to Product, Organization, and FAQ schemas that LLM crawlers cite and summarize.
See Before / After →→Paste your URL. We run a real scan and compare it against the live average across every site scanned on grow.contact.
These bars are a real scan summary. The full report on /check breaks down every signal and ships an actionable fix list.
// Full Technical Specification
Semantic HTML — What We Ship
Every page delivered with <main> wrapping the primary content zone, <article> for standalone content, <section aria-label="..."> for content regions, <nav> for navigation, <aside> for supplementary content. H1 is singular per page and descriptive. H2–H6 hierarchy never skips a level. No presentational divs wrapping semantic content.
JSON-LD — What We Ship
Four schema types minimum on every build: Organization (with sameAs for brand disambiguation), Product or Service (with Offer, pricing, availability), FAQPage (matching visible FAQ content exactly), BreadcrumbList (navigation hierarchy). Additional types based on site type: SoftwareApplication and WebAPI for developer tools, Article with datePublished for blog pages, Person for founder authority signals. All entities nested — not flat.
llms.txt — What We Ship
Spec-compliant llms.txt at site root: H1 matching your site title, blockquote summary of 2–3 sentences, H2 sections linking to Product, Documentation, Company, and Pricing pages. Brand disambiguation included. Linked from HTML <head> as a <link rel="alternate"> tag.
llms-full.txt — What We Ship
Full markdown dump of all site content at /llms-full.txt. Clean markdown only — no HTML tags, no navigation chrome, no footer boilerplate. Pages separated by ---. Token budget managed to stay under 50,000 tokens for marketing sites. Updated at each deployment.
robots.txt — What We Ship
All eight AI crawlers explicitly allowed with correct User-agent strings. GPTBot and OAI-SearchBot separated (training vs. search retrieval). Meta-ExternalAgent blocked for training; FacebookBot allowed for search. Comments inline explaining each directive. Sitemap URL declared at the bottom.
OpenGraph — What We Ship
og:title, og:description (factual, 120–155 characters, not clickbait), og:image (1200×630px), og:type, og:url. Twitter cards on all pages. og:description written as a factual statement — not a teaser. Citation quality is directly affected by how accurately og:description describes the page content.
RSS + Sitemap — What We Ship
XML sitemap at /sitemap.xml with all pages, lastmod dates, and changefreq values. Atom RSS feed at /rss.xml with title, link, pubDate, and first-150-word description for each content page. RSS entry updated at each deployment to signal freshness to RAG pipelines.
Page Speed — What We Ship
TTFB under 200ms. HTML payload under 1MB. LCP under 2.5s. All non-critical JavaScript deferred or lazy-loaded. No inline base64 images in HTML. External font preconnect declared.
// The 48-Hour Process
Step 1 — Brief
Hours 0–2You send positioning doc, existing copy if any, reference sites, and brand assets. We extract: primary ICP, core value proposition, key technical differentiators, pricing structure, and the single primary action each page should drive. We build a creative brief in writing and share it before any design work starts. You confirm or correct. No assumptions.
Step 2 — Architecture
Hours 2–6Before any visual design: site map, content schema, JSON-LD taxonomy, and H1–H6 hierarchy for every page. We decide which schema types each page needs, where the answer-first blocks go, which pages need FAQPage schema, and where llms.txt will link. Architecture is reviewed as a document — not a design mockup.
Step 3 — Design + Build
Hours 6–36Full visual design and code implementation in parallel. Every component is coded — not a template with replaced text. The agent-readability layer is built alongside the visual layer, not bolted on afterward. This is the difference between a site that scores 100/100 and one that scores 60/100 with the same visual design.
Step 4 — Agent Layer
Hours 36–44The final build pass: llms.txt and llms-full.txt written and tested, JSON-LD validated, robots.txt AI directives confirmed, RSS feed validated, page speed measured to TTFB targets. The agent-readability scan is run against the staging URL. If it does not hit 90+, we fix before handover.
Step 5 — Launch + Audit
Hours 44–48Domain handover, DNS configuration, 14-day bug fix window. Final agent-readability score documented and shared. You receive: the live URL, the GitHub repository, the score report, and the Agent-Native Certified badge for your footer.