Weave Code
Oc Sitemap Plugin Laravel Package
vdlp/oc-sitemap-plugin
Generate XML sitemaps for October CMS sites with this plugin, helping search engines discover and index your pages. Simple to install and configure, it keeps your sitemap current so your content ranks better.
A Sitemap plugin for October CMS that generates search-engine-friendly XML sitemaps, helping crawlers discover and index your site’s pages more reliably.
- Generates a standards-compliant XML sitemap
- Integrates with October CMS pages and content
- Provides configurable sitemap settings
- Lightweight and easy to install
- Helps improve search engine visibility
Frequently asked questions about Oc Sitemap Plugin
- What is vdlp/oc-sitemap-plugin and is it a Laravel package?
- It is an October CMS plugin that generates sitemap.xml from CMS content, supported plugin routes, and multilingual pages. October CMS runs on Laravel components, so the plugin is Laravel-adjacent, but it is not a standalone Laravel package and does not ship standard Laravel service providers or publishable config. Use it when October CMS is the serving layer for your site.
- How do I install vdlp/oc-sitemap-plugin in October CMS?
- Install it through the October CMS Plugin Manager or with composer require vdlp/oc-sitemap-plugin, then apply any migrations and configure it in the backend settings. Installation is routine on a supported October build and should not require application code changes. Confirm the declared minimum October CMS and PHP versions for 2.4.0 before you commit, since the changelog does not state them.
- Can I use this sitemap plugin in a plain Laravel application without October CMS?
- No. The oc- prefix and its plugin structure mean it depends on October's plugin layer and backend settings, so composer require into a vanilla Laravel app will not give you a working sitemap generator. For an API-driven or headless Laravel front end, choose a framework-agnostic sitemap generator and invoke it from a scheduled job instead.
- Which October CMS and PHP versions does version 2.4.0 support?
- The 2.4.0 release notes contain only a compare URL, so minimum October CMS and PHP requirements are not documented in the changelog. Check the plugin's version information and composer constraints, then verify against the October build you pin. Treat version compatibility as something to confirm in staging rather than something to assume.
- Does the plugin support multilingual sites and localized URLs?
- Yes, multilingual content support is one of the plugin's advertised capabilities, and it generates sitemap entries for localized pages. The important verification step is confirming that the routes and localized URL variants you actually publish appear correctly and are normalized the way you expect. Sitemap output touches SEO-critical URLs, so it deserves a manual review before launch.
- How do I control which pages and content types appear in the sitemap, and can I extend it for custom content types?
- Configuration happens through the plugin's backend settings, and the plugin integrates with CMS content plus a set of popular plugins. Whether there is a supported extension point for custom content types you own is not documented in the release material, so check the code for override hooks before committing. If no clean extension path exists, a framework-agnostic generator may be the better abstraction boundary.
- How does sitemap caching and regeneration work?
- The plugin handles sitemap generation for your October site, but the exact caching and regeneration behaviour needs verification against your publishing cadence. Confirm when the sitemap is rebuilt after content changes, and clear caches as part of any upgrade. If regeneration lags behind publishing, search engines may see stale URLs.
- How should we test the sitemap before promoting to production?
- Stage the plugin against a copy of your content and diff the generated sitemap.xml before and after any change, checking URL normalization, lastmod values, and localized entries. Validate the XML against the sitemap schema and spot-check that every important route is present and no staging or noindex URLs leak in. Promote only when the output is equivalent or intentionally different.
- Is upgrading from 2.3.0 to 2.4.0 safe, and what changed?
- By semver convention a minor bump suggests additive, backwards-compatible changes, and the expected path is a version pin bump plus a cache clear with no data migration. However, the 2.4.0 release notes contain no changelog entries, migration notes, or deprecation list, and October plugin versioning is not consistently semver-strict. Read the actual diff and stage the upgrade before trusting the convention.
- Is vdlp/oc-sitemap-plugin actively maintained, and what are the alternatives?
- Check commit cadence and issue responsiveness on the GitHub repository before adopting it, because maintenance activity is not established by the release notes. Alternatives include a custom sitemap generator inside October, other October sitemap plugins, or a framework-agnostic generator run from a scheduled job if you need to cover multiple properties. This plugin is the right choice when October CMS is the serving layer and CMS content should drive the sitemap.
Weaver
How can I help you explore Laravel packages today?