Skip to content
Google sitemap builder for Laravel
Branch: master
Clone or download
dwightwatson Merge pull request #64 from simonschaufi/patch-1
lastModified can also be of type DateTime
Latest commit 835db73 Dec 17, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
src lastModified can also be of type DateTime Dec 17, 2018
tests Use camelCase Jul 13, 2018
.gitignore Update docblocks Jul 13, 2018
.travis.yml Don't test against HHVM Jun 30, 2017
LICENSE.txt Add a licence to the package Feb 3, 2014 Fix a typo Nov 20, 2017
phpunit.xml Whitelist PHP source files for testing Feb 7, 2016

Sitemap for Laravel

Build Status Total Downloads Latest Stable Version Latest Unstable Version License

Sitemap is a package built specifically for Laravel that will help you generate XML sitemaps for Google. Based on laravel-sitemap this package operates in a slightly different way to better fit the needs of our project. A facade is used to access the sitemap class and we have added the ability to produce sitemap indexes as well as sitemaps. Furthermore, it's tested.

Read more about sitemaps and how to use them efficiently on Google Webmaster Tools.

Installation for Laravel 5.5

Simply require the package and let Composer get the latest compatible version for you.

composer require watson/sitemap

Since Laravel 5.5 uses Package Auto-Discovery, you don't have to edit anything in config/app.php

Installation for Laravel 5.*

Simply require the package and let Composer get the latest compatible version for you.

composer require watson/sitemap

Now, add the service provider to your config/app.php file.


And finally add the alias to the facade, also in config/app.php.

'Sitemap' => Watson\Sitemap\Facades\Sitemap::class

Installation for Laravel 4.*

Simply pop the version constraint in your composer.json file and run composer update (hoever your Composer is installed).

"watson/sitemap": "1.1.*"

For the documentation, have a look through the 1.1 branch.


Creating sitemap indexes

If you have a large number of links (50,000+) you will want to break your sitemaps out into seperate sitemaps with a sitemap index linking them all. You add sitemap indexes using Sitemap::addSitemap($location, $lastModified) and then you return the sitemap index with Sitemap::renderSitemapIndex(). The $lastModified variable will be parsed and converted to the right format for a sitemap.

Here is an example controller that produces a sitemap index.

namespace App\Http\Controllers;

use Sitemap;

class SitemapsController extends Controller
    public function index()
        // Get a general sitemap.

        // You can use the route helpers too.

        // Return the sitemap to the client.
        return Sitemap::index();

Simply route to this as you usually would, Route::get('sitemap', 'SitemapsController@index');.

Creating sitemaps

Similarly to sitemap indexes, you just add tags for each item in your sitemap using Sitemap::addTag($location, $lastModified, $changeFrequency, $priority). You can return the sitemap with Sitemap::renderSitemap(). Again, the $lastModified variable will be parsed and convered to the right format for the sitemap.

If you'd like to just get the raw XML, simply call Sitemap::xml().

Here is an example controller that produces a sitemap for blog posts.

namespace App\Http\Controllers;

use Post;
use Sitemap;

class SitemapsController extends Controller
    public function posts()
        $posts = Post::all();

        foreach ($posts as $post) {
            Sitemap::addTag(route('', $post), $post->updated_at, 'daily', '0.8');

        return Sitemap::render();

If you just want to pass a model's updated_at timestamp as the last modified parameter, you can simply pass the model as the second parameter and the sitemap will use that attribute automatically.

If you're pulling a lot of records from your database you might want to consider restricting the amount of data you're getting by using the select() method. You can also use the chunk() method to only load a certain number of records at any one time as to not run out of memory.

Image sitemaps

You can use Google image extensions for sitemaps to give Google more information about the images available on your pages. Read the specification

Images are associated with page and you can use up to 1000 images per page.

Here is an example of adding image tag to usual page tag.

namespace App\Http\Controllers;

use Page;
use Sitemap;

class SitemapsController extends Controller
    public function pages()
        $pages = Page::all();

        foreach ($pages as $page) {
            $tag = Sitemap::addTag(route('', $page), $page->updated_at, 'daily', '0.8');

            foreach ($page->images as $image) {
                $tag->addImage($image->url, $image->caption);

        return Sitemap::render();

Here is the full list of arguments to add an image to a tag.

$tag->addImage($location, $caption, $geoLocation, $title, $licenceUrl);


To publish the configuration file for the sitemap package, simply run this Artisan command:

php artisan config:publish watson/sitemap

php artisan vendor:publish --provider="Watson\Sitemap\SitemapServiceProvider"

Then take a look in config/sitemap.php to see what is available.


By default, caching is disabled. If you would like to enable caching, simply set cache_enabled in the configuration file to true. You can then specify how long you would like your views to be cached for. Keep in mind that when enabled, caching will affect each and every request made to the sitemap package.

Multilingual tags

If you'd like to use a mutlilingual tag, simply pass an instance of one to the addTag method. Below is a crude example of how you would pass alternate tag locations for different languages.

Sitemap::addTag(new \Watson\Sitemap\Tags\MultilingualTag(
        'en' => $location . '?lang=en',
        'fr' => $location . '?lang=fr'
You can’t perform that action at this time.