> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/web/seo>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/web/seo.mdx>

---

# Web SEO API

Pass a URL; get back what a crawler sees on the page, with pass or fail checks you can act on.

`GET /v1/web/seo` reads a public page's HTML the way a search crawler first does, before any JavaScript runs, and returns an on-page audit: the final URL, its HTTP `status` and every `redirects` hop, then under `audit` the title and meta description with their lengths, robots directives from the meta tag and the `X-Robots-Tag` header, the canonical URL, hreflang alternates, headings by level, Open Graph and Twitter card tags, JSON-LD blocks and microdata types, links (internal, external, nofollow), images and their alt text, word count, and `checks`: true or false flags such as `hasH1`, `titleTooLong`, `canonicalIsSelf`, `noindex` and `imagesMissingAlt`.

Lists are capped (300 links, 200 images, 50 headings per level) while the counts stay exact. A page that answers 404 or 500 is still audited, so you can check broken pages too.

A call costs 1 credit, which reads about 1.6 MB on the standard proxy, far more than most pages' HTML. The page is tried on a datacenter proxy first and moves up to residential or mobile only if the site blocks it; `proxy` caps how far it goes and `maxCredits` (up to 25) raises the budget. Read `meta.creditsCharged` on every response.

## Request

- **Endpoint:** `GET /v1/web/seo`
- **Credits:** 1 credit
+24 credits for maxCredits
Max 25 credits
You're only charged for what's returned
- **Input:** by URL
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/web/seo/get)
- **Platform page:** [/platforms/web](https://www.socialfetch.dev/platforms/web)

## FAQ

### What does the Web SEO API return?

lookupStatus, the requested url, finalUrl, status, redirects, the proxy tier used, budgetExceeded, bytesTransferred, and audit: title, metaDescription, robots, canonical, lang, hreflang, headings, openGraph, twitterCard, structuredData, links, images, wordCount and checks.

### How do I call it?

Send GET /v1/web/seo with x-api-key and a public url. Optional: proxy and maxCredits.

### How much does it cost?

1 credit per call by default, which loads about 1.6 MB on the standard proxy. A page that needs more stops early (budgetExceeded: true) unless you raise maxCredits (up to 25); then you're charged only for the data it uses. Blocked sites move up to residential or mobile proxies automatically; those use the budget about nine times faster. meta.creditsCharged is the billing source of truth.

### Does it run JavaScript?

No. It audits the HTML the server sends, which is what search crawlers index first. Titles, canonicals or links that a page only adds with JavaScript won't appear; GET /v1/web/html returns the rendered page.

### What does lookupStatus restricted mean?

Bot protection blocked the page on every proxy tier allowed, so audit is null. It bills like the other web routes. If you set proxy=datacenter, try without it.

### Can I audit a whole site?

List the site's URLs with GET /v1/web/map, then audit the ones you need with GET /v1/web/seo, one call per page.
