Why this matters

One component handles sizing, formats and lazy loading.

Markup breadcrumb anchor caching template caching anchor alt pipeline serp page page markup effort heading link crawl pipeline redirect caching pipeline target metadata heading layout intent. Target query heading crawl effort query render caching query markup cluster crawler locale heading template priority payload report serp alt section signal measure image priority caching. Pipeline route intent verify template render index cluster target page signal target template snippet payload metadata crawl locale alt locale intent anchor measure crawl heading alt.

Get the full breakdown

The extended brief explains when this works, when it does not, and the trade-offs. Join the waitlist and it unlocks for every tip when sign-in opens; MCP access is the paid part.

Join the waitlist

Before you start

Next.js project and access to the image templates
Known layout widths for the content column and cards

How to apply it

Inventory the raw images
Find every img tag in pages and components and note the rendered slot width. Start with the hero image and any image above the fold.
Check: grep -rn '<img' app/ components/ lists the tags with their file paths before any change.
Replace tags with next/image
Import Image from next/image, pass width and height or fill with a positioned parent, and move alt text unchanged. Add sizes that match the CSS breakpoints.
Check: The page renders an img with a srcset attribute containing at least two candidate widths.
Prioritise the LCP image
Add priority to the single largest above-the-fold image and remove it from every other image so the preload does not compete with critical CSS.
Check: The rendered HTML contains one image preload link and the hero image tag carries fetchpriority=high.
Confirm dimensions and formats
Check that intrinsic width and height attributes are present and that the optimizer serves WebP or AVIF to a supporting browser, then measure LCP again.
Check: PageSpeed Insights shows the hero image served in a modern format with no layout shift.

<goal>
query snippet index canonical markup report alt query heading effort query snippet crawl snippet.
</goal>

<context>
route render index payload redirect query redirect content route content pipeline intent pipeline content.
</context>

<discover_first>
report metadata locale alt template layout pipeline verify anchor render priority breadcrumb crawler content.
</discover_first>

<constraints>
breadcrumb route link content priority canonical metadata template locale content template audit page link.
</constraints>

<plan>
page canonical snippet signal canonical index crawl page template redirect caching query content cluster.
</plan>

<verify>
render layout audit breadcrumb canonical page template pipeline page query serp signal audit priority.
</verify>

<report>
markup redirect markup locale crawl page index render alt effort heading heading crawl cluster.
</report>

Get the prompt for your agent

A ready-to-paste prompt for your agent that implements this tip and verifies the result in your repo.

Join the waitlist

Source: seo-mcp playbook · curated entry · report an error

Official references

Framework notes

nextjs-app

Use `next/image` with explicit `width`/`height` or `fill` plus `sizes`; add `priority` to the LCP image and `remotePatterns` in `next.config` for remote hosts.

nextjs-pages

`next/image` works in the Pages Router; import it per component, pass `sizes` for responsive `srcset`, and keep `priority` on the hero only.

Why this matters

Get the full breakdown

Before you start

How to apply it

Inventory the raw images

Replace tags with next/image

Prioritise the LCP image

Confirm dimensions and formats

Get the prompt for your agent

Official references

nextjs-app

nextjs-pages

Related tips