Skip to content
DevMarDe
Marketing · Next.js

Marketing for Next.js

SaaS products, marketing sites owned by engineering teams, and everything we build ourselves. See which channel paid for itself: search, paid or content. On Next.js specifically, this is what changes.

report.devmarde.com/w37Weekly report · Monday
Qualified enquiries · week 37
31 +6 vs last week
w31
w32
w33
w34
w35
w36
w37
ChannelEnq.Cost / enq.
Search12£38
Paid search9£71
AI assistants6£0
Referral3£0
Paid social1£210
Paid social paused Thursday. Budget moved to product-line search.
200
signals checked per audit
6
assistants tracked
Weekly
reporting cadence

What Next.js gets right, and what it does not

  • The Metadata API covers titles and Open Graph but not JSON-LD; schema needs a script tag in the layout or page.
  • Vercel's bot protection is off by default; if Attack Challenge Mode is on, AI crawlers get a challenge page.
  • generateStaticParams makes programmatic pages cheap, which is why thin templated pages are the common failure.

AI visibility on Next.js

  • llms.txt. Place llms.txt in /public. It deploys with the site and is served as text/plain.
  • Schema. Render an @graph in app/layout.tsx for Organization and WebSite, and page-level blocks in each page component.
  • Crawlers. Export a robots() function from app/robots.ts with explicit allow rules per AI user agent.

What we would ship first

  • Search and GEOClassic search plus the entity, schema and answer-structure work that decides whether assistants can read you at all.
  • Paid mediaGoogle, Meta and LinkedIn spend that stops when it stops working. Weekly reporting, no annual lock-in.
  • ContentGuides, comparisons and answer pages written to be quoted, with an author and a date on every one.
  • Programmatic SEOTemplated pages built from real data, not spun text. Platform, industry and location variants that each say something specific.

How the engagement runs

  • Baseline. Run the audit, read the analytics, list the queries you should own and do not. One document.
  • Fix the plumbing. Tracking, schema, crawler access and the pages every channel lands on. Two to three weeks.
  • Ship channels. Search, paid and content go live in the order the baseline justified.
  • Report weekly. One page, one number, every Monday. Spend moves toward what worked.
100
Lighthouse performance on this site. Same for SEO, accessibility and best practices
5
products of our own in production
3
practices, each with a named lead
1 day
reply time on every enquiry
4.9
from 9 reviews

Questions people ask

Do you work inside our existing Next.js setup?
Yes. The scoping sprint starts with what is there. We extend Next.js where that is honest and propose a move only when the platform is the constraint.
Can you fix AI crawler access on Next.js?
Export a robots() function from app/robots.ts with explicit allow rules per AI user agent.
Do you handle media spend?
We run the accounts. Spend is billed to your card by the platforms, so there is no markup and no lock-in.
What is GEO?
Generative engine optimisation: the technical and content work that makes AI assistants cite you when they answer a question in your category.