XML Sitemap
iContentForge automatically generates a comprehensive XML sitemap for every project you create. This sitemap is a critical SEO tool that helps search engines like Google discover, crawl, and index your published articles efficiently.
The sitemap is dynamically updated as new articles are published through the platform, ensuring search engines always have an accurate map of your content.
Accessing Your Sitemap
Your project's sitemap is publicly accessible at a dedicated endpoint. You can find the URL in your project's Settings > General tab.
Location of the Sitemap URL in Project Settings
The sitemap URL follows this pattern:
https://app.icontentforge.com/api/public/sitemap/:projectId
Replace :projectId with your actual project ID (a UUID). You can also copy the full URL directly from your project settings.
You can validate your sitemap using online tools like the XML Sitemap Validator or directly within Google Search Console to ensure it's formatted correctly.
Sitemap Structure & Fields
The generated XML sitemap conforms to the sitemaps.org protocol. It includes the following standard fields for each published article URL (<url> entry):
| Field | Description | Example Value in iContentForge |
|---|---|---|
<loc> | The full, absolute URL of the article. | https://yourblog.com/your-article-slug |
<lastmod> | The date the article was last modified. Uses the article's lastUpdatedAt timestamp in ISO 8601 format (YYYY-MM-DD). | 2024-01-15 |
<changefreq> | An indication of how frequently the page is likely to change. iContentForge sets this to monthly by default for all articles. | monthly |
<priority> | The priority of this URL relative to other URLs on your site. iContentForge sets a default priority of 0.8. | 0.8 |
Here is an example of what a single entry in your sitemap will look like:
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://yourblog.com/best-ai-content-tools</loc>
<lastmod>2024-01-15</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<!-- More URLs will be listed here -->
</urlset>
The changefreq and priority values are set as sensible defaults for automated content. These are hints for search engines, not direct commands. The lastmod date is crucial as it helps search engines understand which content is fresh.
Submitting to Google Search Console
To ensure Google quickly discovers and indexes your new content, you should submit your sitemap URL to Google Search Console (GSC).
- Log in to your Google Search Console account.
- Select the property (website) that matches the domain your iContentForge project is publishing to.
- In the left sidebar, navigate to Sitemaps under the "Indexing" section.
- In the input field labeled "Add a new sitemap," paste the full sitemap URL you copied from iContentForge (e.g.,
https://app.icontentforge.com/api/public/sitemap/your-project-id). - Click Submit.
Submitting a sitemap URL in Google Search Console
After submission, Google will show the sitemap status as "Pending" before updating to "Success" once it has been processed. It will also show the number of URLs discovered.
Your sitemap must be publicly accessible for Google to fetch it. If your WordPress or CMS site is behind a login or firewall, the sitemap submission may fail. Ensure your published articles are on a publicly available domain.
Best Practices
- Resubmit After Major Updates: While Google crawls sitemaps periodically, you can manually click "Resubmit" in GSC if you publish a large batch of new articles and want to prompt a faster re-crawl.
- Monitor for Errors: Regularly check the "Sitemaps" section in GSC for any errors, such as URLs being blocked by
robots.txtor returning 4xx/5xx status codes. - Combine with Internal Links: For the strongest SEO results, use iContentForge's Silo Radar to build a robust internal link structure alongside your sitemap.
Next Steps
- Learn how to automate publishing with CMS Connectors.
- Understand your content's link structure with the Silo Radar.
- Configure the timing of your publications using Drip Feed.