メニュー
Use when auditing, planning, or implementing SEO in a Laravel app — crawlability, indexability, JSON-LD structured data in Blade, Core Web Vitals, on-page tags, keyword mapping, competitor gap analysis, E-E-A-T content quality, and measurement.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | seo |
| description | Use when auditing, planning, or implementing SEO in a Laravel app — crawlability, indexability, JSON-LD structured data in Blade, Core Web Vitals, on-page tags, keyword mapping, competitor gap analysis, E-E-A-T content quality, and measurement. |
| license | MIT |
| metadata | {"author":"Petr Král (pekral.cz)"} |
@rules/laravel/laravel.mdc for routing, Blade, and asset conventions.@rules/security/frontend.md — never inject unsanitized user content into JSON-LD, meta tags, or <head>; escape every dynamic value.robots.txt allows important pages and blocks low-value surfaces (e.g. /admin, filtered listing permutations). In Laravel, serve a static public/robots.txt or a route that renders one per environment (block everything on staging).noindex.Redirect:: rules and web-server rewrites for stacked redirects.www vs apex). Enforce with a single canonical host and HTTPS redirect.route('post.show', $post).hreflang when locales exist.spatie/laravel-sitemap package to crawl and emit sitemap.xml.Walk these every audit; each item maps to a concrete file, route, or response to inspect — never report a category without naming where it occurs.
| Check | What to look for | Where in Laravel |
|---|---|---|
| Crawl errors | 4xx/5xx on linked URLs | server logs, route list, php artisan route:list |
| Broken links | dead internal/outbound hrefs | Blade views, content models, a crawl pass |
| Redirect chains | 2+ stacked hops | Redirect:: rules, web-server rewrites |
| Mixed content | http:// assets on an HTTPS page | Blade asset refs; force asset()/secure_url() |
| Duplicate content | same intent on multiple URLs | facets, pagination, casing/slash variants |
| Thin content | low-value near-empty pages | auto-generated tag/archive pages |
| Orphan pages | published but unlinked internally | compare sitemap/routes against internal links |
href pointing at it cannot be discovered by crawlers following links — surface it and add an internal link or drop it from the sitemap.http:// asset is downgraded and may be blocked by the browser. Derive asset URLs from asset() / secure_url() so they inherit the request scheme.{{-- resources/views/layouts/app.blade.php (inside <head>) --}}
<title>@yield('title', config('app.name'))</title>
<meta name="description" content="@yield('meta_description', '')">
<link rel="canonical" href="{{ $canonical ?? url()->current() }}">
@hasSection('noindex')
<meta name="robots" content="noindex,nofollow">
@endif
@stack('schema')
{{-- a page view --}}
@section('title', $post->title . ' | ' . config('app.name'))
@section('meta_description', Str::limit(strip_tags($post->excerpt), 155))
@php($canonical = route('post.show', $post))
Targets: LCP < 2.5s, INP < 200ms, CLS < 0.1.
@vite) so they cache long-term. Use loading="eager" and fetchpriority="high" on the LCP image; loading="lazy" on below-the-fold images.width/height on images, and avoid injecting content above existing content. Tailwind aspect-* utilities help reserve space.font-display: swap.Emit JSON-LD in the layout via a pushed stack so each page contributes its own schema. Match schema to content that is actually present.
Organization or local business schema where appropriate.Article / BlogPosting.Product and Offer.BreadcrumbList.FAQPage only when the content truly matches.{{-- a page view --}}
@push('schema')
<script type="application/ld+json">
{!! json_encode([
'@context' => 'https://schema.org',
'@type' => 'Article',
'headline' => $post->title,
'author' => ['@type' => 'Person', 'name' => $post->author->name],
'publisher'=> ['@type' => 'Organization', 'name' => config('app.name')],
'datePublished' => $post->published_at->toIso8601String(),
], JSON_UNESCAPED_SLASHES | JSON_UNESCAPED_UNICODE) !!}
</script>
@endpush
Build the array with json_encode (never string-concatenate user input) so values are escaped and the document stays valid. Validate the emitted markup with Google's Rich Results Test before relying on it.
H1 per page.H2/H3 reflect real content hierarchy; do not pick heading levels for visual styling.Title: Primary Topic - Specific Modifier | Brand
Meta: Action + topic + value proposition + one supporting detail
Use competitors to find concrete, page-level opportunities — never to copy.
[gap type] target query/topic → owning URL → concrete change, so it slots straight into the audit output below.Search engines reward Experience, Expertise, Authoritativeness, and Trustworthiness. Tie each signal to something on the page.
Article.author in JSON-LD plus a visible byline) and first-hand detail, not paraphrased generalities.Every recommendation needs a measurable outcome; pick the metrics that match the change and capture a baseline before shipping.
Validate audits and findings with real tools rather than asserting them:
php artisan route:list for the public surface, a sitemap build for the intended index set.[HIGH] Duplicate title tags on product pages
Location: resources/views/products/show.blade.php
Issue: @section('title') falls back to the app name for every product, weakening relevance and creating duplicate signals.
Fix: Render a unique title from the product name and primary category.
Measure: distinct title coverage in Search Console; expect duplicate-title warnings to drop.
| Anti-pattern | Fix |
|---|---|
| keyword stuffing | write for users first |
| thin near-duplicate pages | consolidate or differentiate them |
| schema for content that is not present | match schema to reality |
| advice without checking the actual page | read the real Blade view first |
| generic "improve SEO" output | tie every recommendation to a page or asset |
| hand-built canonical URLs | derive from named routes |
| buying or exchanging links | earn links through useful content |
| recommendation with no metric | state the metric and baseline to verify it |
noindex.Use when reviewing HTTP API design in a PR or change set — endpoints, routes, HTTP methods, status codes, idempotency, and input validation. Treats the API as a consumer-facing contract and flags resource-orientation, method-semantics, status-code, and trust-boundary violations. Read-only.
Use when checking that the pull request implementation actually fulfills the business requirements stated in the linked issue or task. Returns a plain-language markdown block that is the Functional review half of the two-part CR output (`@rules/code-review/general.mdc` Two-part CR output — Technical & Functional review): a full checklist of every extracted acceptance criterion with its status (Met / Not met / Partial / Divergent) and an explicit Goal met: Yes/No verdict, rendered on every run that has a linked tracker — including the fully affirmative report when every requirement is satisfied. No local file is created and the block is not embedded in the GitHub PR comment.
Use when run code review for a Bugsnag error and publish results to the linked GitHub PR and the Bugsnag error
Use when perform code review for GitHub pull requests and post findings as PR comments plus a non-technical summary to every linked issue
Use when run code review for JIRA issues and publish results to GitHub PR and JIRA
Use when senior PHP code review focused on architecture, business logic, and risk detection. Read-only.