# Rankbeam > SEO for Laravel: layered meta resolution, Open Graph / Twitter Cards, JSON-LD schema graph, and XML sitemaps. Documentation for the Rankbeam Laravel SEO family. Every page below is also available as raw Markdown at the same URL with a `.md` suffix. ## Getting started - [Why Rankbeam](https://docs.rankbeam.dev/guide/why-rankbeam.md): Most Laravel apps don't have an "SEO package." They have an SEO stack: a package that stores meta per model, a second package that adds the fields to Filament, a third that scans pages, and then a… - [Installation](https://docs.rankbeam.dev/guide/installation.md): Install rankbeam/laravel-seo with Composer, publish the config, and register the middleware — requirements and setup for Laravel 11, 12, and 13. - [Quickstart](https://docs.rankbeam.dev/guide/quickstart.md): Five minutes from install to fully rendered meta tags. - [Run the demo](https://docs.rankbeam.dev/guide/demo.md): The fastest way to see Rankbeam working on real pages — without wiring it into your own app first — is the runnable demo. ## Concepts - [Resolver precedence](https://docs.rankbeam.dev/concepts/resolver-precedence.md): Every effective SEO value — title, description, canonical, robots, images — is produced by SEOResolver merging six layers. ## Guides - [Blade](https://docs.rankbeam.dev/guide/blade.md): For classic server-rendered apps, the package ships seven Blade directives. - [Inertia & JSON APIs](https://docs.rankbeam.dev/guide/inertia-json.md): The same resolved SEOData that powers @seo renders to structured arrays — one source of truth whether the head is built by Blade, Vue, React, Svelte, or a separate frontend consuming your API. - [Livewire](https://docs.rankbeam.dev/guide/livewire.md): The @seo Blade directives are framework-generic — they emit plain HTML into the head, so they work in any Livewire app the same way they work in Blade. - [Schema graph (JSON-LD)](https://docs.rankbeam.dev/guide/schema.md): Search engines read JSON-LD best when the nodes reference each other — the Organization publishes the WebSite, the WebSite contains the WebPage, the WebPage is about the Article. - [Sitemap registry](https://docs.rankbeam.dev/guide/sitemaps.md): The package generates XML sitemaps (one file per source plus an index) and serves them at /sitemap.xml and /sitemap-{name}.xml. - [AI crawler control](https://docs.rankbeam.dev/guide/ai-crawlers.md): The AI answer engines crawl the web with named bots, and they read robots.txt to decide what they may use. - [Indexing guard](https://docs.rankbeam.dev/guide/indexing-guard.md): A staging or local copy of your site leaking into Google is one of the most common — and most damaging — SEO mistakes: duplicate content competing with your real pages, a private environment sittin… - [Markdown for bots](https://docs.rankbeam.dev/guide/markdown-for-bots.md): AI crawlers and answer engines parse content far more reliably from clean markdown than from a page of application HTML. - [Generated OG images](https://docs.rankbeam.dev/guide/og-image.md): A page with no social card falls back to one shared default_og_image — the same picture on every share. - [Free SEO audit](https://docs.rankbeam.dev/guide/audit.md): php artisan seo:audit answers one question in one command, for free: what's wrong with my SEO right now? - [Explain resolution](https://docs.rankbeam.dev/guide/explain.md): Rankbeam resolves a page's SEO through a layered precedence chain — config, database defaults (global / model-type / route), computed model values, then explicit seo_meta — followed by post-process… - [Migrating from WordPress](https://docs.rankbeam.dev/guide/migrate-from-wordpress.md): Moving a content site off WordPress? - [WordPress migration runbook](https://docs.rankbeam.dev/guide/wordpress-migration-runbook.md): A step-by-step, low-risk procedure for replacing a legacy WordPress SEO stack (Yoast or Rank Math) with Rankbeam on a real, live site. - [Migrating from other packages](https://docs.rankbeam.dev/guide/migrate-from-other-packages.md): Already using another SEO package? - [Filament admin fields](https://docs.rankbeam.dev/guide/filament.md): The free rankbeam/laravel-seo-filament package adds a complete SEO section to any Filament resource form — two lines per resource. ## Pro - [Installing Pro](https://docs.rankbeam.dev/pro/installation.md): rankbeam/laravel-seo-pro adds queued site scans with issue tracking, a redirect manager, and a 404 monitor on top of the core package. - [Production setup](https://docs.rankbeam.dev/pro/production.md): Pro's day-to-day work — site scans, the broken-link crawler, optional redirect-hit flushing, 404 pruning — runs on Laravel's queue and scheduler. - [Headless usage](https://docs.rankbeam.dev/pro/headless.md): Every Pro feature — scanning, redirecting, 404 logging — runs headless: it lives in the engine and needs no Filament. - [Scan issues](https://docs.rankbeam.dev/pro/scan-issues.md): Every problem the Pro scan reports is a stable issue code drawn from a single registry, Rankbeam\Seo\Pro\Scanning\IssueRegistry. - [SEO score](https://docs.rankbeam.dev/pro/scoring.md): The Pro scan gives every page a 0-100 SEO score — the single number a RankMath or Yoast migrant looks for. - [On-page checklist](https://docs.rankbeam.dev/pro/on-page-checklist.md): The on-page checklist is the live editorial loop a RankMath or Yoast user expects: pick a focus keyword, and get a traffic-light list of "is this page optimised for it?" checks — keyword in the tit… - [Broken-link crawler](https://docs.rankbeam.dev/pro/broken-links.md): A bounded, resumable crawler that walks your site, follows the links on each page, and records the ones that don't resolve — broken internal links (a dead route on your own host, fixable in one cli… - [Search Console](https://docs.rankbeam.dev/pro/search-console.md): A read-only Google Search Console panel: your top queries and pages with impressions, clicks, CTR and average position, joined to the pages the scanner already knows about — so you can see "this pa… - [IndexNow](https://docs.rankbeam.dev/pro/indexnow.md): Instead of waiting for a crawler to find a changed page, IndexNow lets you tell the search engines the moment a URL is published or updated. - [AI-bot monitor](https://docs.rankbeam.dev/pro/ai-bot-monitor.md): The AI crawler control feature (core) decides what robots.txt tells the AI crawlers. - [MCP server](https://docs.rankbeam.dev/pro/mcp.md): The Rankbeam MCP server lets an AI assistant read — and optionally edit — a site's SEO over the Model Context Protocol. - [AI assist](https://docs.rankbeam.dev/pro/ai-assist.md): Optional, bring-your-own-key AI assistance: title and meta-description suggestions, plain-language explanations of scan issues, a one-click description rewrite, and a structured-data (schema.org) s… ## Reference - [Configuration](https://docs.rankbeam.dev/reference/configuration.md): Every option in config/seo.php, grouped by resolver layer, with the shipped default for each value. - [Upgrading from v1](https://docs.rankbeam.dev/guide/upgrade-from-v1.md): v2.0.0 renames the package to rankbeam/laravel-seo and carves it down to a focused core: meta resolution, rendering, JSON-LD, and sitemaps. ## Blog - [Canonical URLs in Laravel](https://docs.rankbeam.dev/blog/canonical-urls-in-laravel.md): A production-tested canonical policy for Laravel apps — when to derive, when to set explicitly, and what to do with query strings. - [JSON-LD schema graphs](https://docs.rankbeam.dev/blog/json-ld-schema-graphs-in-laravel.md): How to emit a connected JSON-LD graph (Organization → WebSite → WebPage) from Laravel, and why your json_encode flags are a security decision. ## Contributing - [Rendering contract](https://docs.rankbeam.dev/contributing/rendering-contract.md): This is the single canonical checklist every front-end stack's head must satisfy when it renders Rankbeam SEO data.