Laravel provides elegant solutions for problems that often become more complex as a project grows. In this category, I share practical observations from real development: working with Pipelines, services, queues, events, testing, and other architectural techniques that help keep applications maintainable and easy to evolve.
In ICanUp, visible breadcrumbs and BreadcrumbList JSON-LD describe the same page hierarchy. I show how I connect navigation with structured data, generate sequential positions, use localized canonical URLs, and avoid creating a separate SEO hierarchy on top of application breadcrumbs.
In ICanUp, BlogPosting JSON-LD connects an article not only to its SEO metadata but also to a real author entity. I show how I represent the author as a Person, keep structured data aligned with the canonical URL and localized metadata, and render it directly in the SSR HTML.
In a multilingual Laravel project, x-default can easily look like another language version. In ICanUp, I use it differently: x-default points to the default locale URL. I walk through the real HreflangService, its relationship with canonical URLs, and the edge cases across different content types.
In ICanUp, Posts and Categories use one shared slug while localized URLs differ through the locale prefix and localized content. I explain why I moved away from translated slugs, how the shared-slug model simplified routing, hreflang, sitemaps, and IndexNow, and when language-specific slugs can still be the better choice.
In ICanUp, a delayed IndexNow job is scheduled for a future published_at, but the publication time, slug, or public state may change before the job runs. Using real Laravel code, I show how the job rechecks current state, rejects stale scheduling, and generates current URLs instead of trusting an old snapshot.
In ICanUp, I run IndexNow notifications and related queue operations only after a successful database commit. Using real Laravel code, I show why dispatching work inside a transaction can expose uncommitted state or survive a rollback, and how DB::afterCommit() creates a clear boundary between database state and external side effects.
In a multilingual Laravel project, having separate UK and EN URLs is not enough. I explain how I configured canonical and hreflang in ICanUp, connected language versions, added x-default, and verified that search engines receive the correct relationship between localized pages.
While working on my sitemap, I found a subtle problem: a public page could change through its translation table while the parent model updated_at stayed unchanged. This article shows how I verified the case and chose the correct lastmod for localized pages.
I did not want to notify Bing manually every time I published or updated a page on ICanUp. I integrated IndexNow into Laravel with a key endpoint, HTTP client, queued submission job, localized URL generation for posts, pages and categories, deduplication, and tests.
Normal pages worked, the browser console was clean, yet Laravel logs still showed an Inertia SSR exception. This article walks through a real case where a controlled request and a log marker isolated the problem to the 404 error-page flow.
Laravel Pint was already installed in my project, but PHP-CS-Fixer was still running alongside it with its own rules. I decided to remove the duplication, keep one formatter, and standardize the PHP codebase with Pint.
Ziggy can work perfectly in the browser while still failing during SSR. This article explores how to keep one consistent routing contract across Laravel, Blade, Vue and Inertia SSR without creating separate route contexts.