Manage project pages and sitemaps

Use Project pages in the Project Manager to choose which website paths receive individual analytics. You can also recheck the sitemap and import new pages for individual analytics here.

You need your owner account for the Project Manager. Select the correct project first, then open Project pages in its menu. Locked and deleted projects cannot be edited here.

Understand the overview

Three values appear at the top:

Display	Meaning
Individual analytics active	Number of pages currently enabled for individual analytics.
Page places in your plan	How many pages your project can analyse individually at the same time.
Saved pages	Existing pages and retained disabled paths. Sitemap suggestions not yet imported are not included here.

The table shows the path, individual analytics status, source and current sitemap membership, plus Total views and Last seen. These counts are stored browser page views from both tracking modes. They are neither visitor counts nor crawler counts.

This management view does not use the date range selected in the Analytics App. Do not directly compare its overall counters with a daily or monthly app value.

Find and select pages

1. Use Find a page for part of a path, or URL starts with for a section such as /blog/.
2. Narrow the results using Individual analytics, Source and Current sitemap if needed. Multiple filters apply together.
3. Choose a sort order: URL, most views or most recently visited. Per page offers 25, 50 and 100 entries.
4. Select individual pages or use the table-header checkbox for the visible rows.

Select all results covers every result of the current filters, including other table pages. Check the displayed selection count before a bulk change. Clear selection removes the selection; Reset resets the filters.

Disable a page

1. Find the required path.
2. Choose Disable in its row. For several paths, select them first and use the bulk button with the same name.
3. Review the confirmation dialog and choose Save change.

The change applies to new requests once saved. It deletes neither the page on your website nor its existing statistics.

Disabling individual analytics does not stop tracking

New views of a disabled path still contribute to overall traffic, including recorded active time. They are collected in aggregate rather than attributed individually to that path. Its page slot becomes available; the traffic limit still applies.

The tracker or crawler does not automatically reactivate a deliberately disabled path. You decide when to resume its individual analytics.

Enable a page again

Choose Enable for an inactive page and confirm with Save change. This requires an available page slot. New requests are then attributed to the individual path again.

Values collected in aggregate while it was disabled are not redistributed to that path afterwards.

Example: A page has 100 individually recorded views. Another 30 occur while it is disabled, followed by 20 after reactivation. Its individual analytics can then show 120 views; the intervening 30 remain in aggregate values. All 150 views can contribute to overall traffic.

When the page limit is reached

Only active individual pages occupy page slots. When slots run out, choose which pages you want to analyse individually. You can disable other pages or reduce the proposed selection.

The entire selection must fit within available slots for a bulk activation. If there is insufficient capacity, the change is not partially applied. Projects already above their limit are not automatically reduced either; additional activations are rejected, while disabling remains possible.

Page capacity and traffic usage are separate limits. Disabling a page reduces the number of active individual pages but does not exclude its future views from overall traffic.

Check the sitemap again

1. Open Check sitemap under Project pages.
2. Choose Check sitemap again and wait for the result.
3. Read the time of the last successful check and its summary: detected sitemap pages, pages not yet imported and entries removed since the previous result.

The check uses your project's saved website address. It updates current sitemap membership. It neither confirms tracking installation on every page nor generates visitor views itself.

The Refresh button at the top of page management only reloads the saved management data. It does not fetch the sitemap again.

Import new sitemap pages

1. After a successful check, choose Show new sitemap pages. Alternatively, select Current sitemap → New in sitemap.
2. Review the suggested paths. They initially have the status New.
3. Choose Import for one page. For several pages, select them and choose Enable; Select all results selects the entire filtered set.
4. Check the count and available page slots, then confirm with Save change.

Only confirmed import creates the new suggestions as active individual pages and occupies page slots. Rechecking the sitemap alone does not import them. Known paths are treated as existing pages; deliberately disabled pages need to be enabled again explicitly if desired.

A sitemap is optional when creating a project. Your website can be tracked without a successful import. Whether more paths are discovered automatically as individual pages depends on project configuration and available slots. For a fixed selection, consider automatic discovery by browsers and crawlers separately.

Distinguish source from current sitemap membership

Source describes whether a page originally came from a sitemap or was discovered automatically. Current sitemap describes its membership in the last successfully saved check.

Example	Interpretation
Discovered automatically and currently included	The path was originally recorded automatically and now also appears in the sitemap.
Sitemap source, currently not included	The known path is absent from the last successful result. Its source still remains sitemap.
New in sitemap	A detected suggestion has not yet been imported as a project page.

An entry removed from the sitemap is not automatically deleted or disabled. Existing statistics and your activation setting are retained. Decide whether you still want to analyse the page individually.

Without a complete saved result, the manager shows current membership as Not checked.

Problems checking or importing

Message or situation	Next step
No usable sitemap, fetch failure or invalid XML	Check your website's sitemap and retry. The last complete result is preserved.
A check exceeds a protective limit or takes too long	Read the specific notice and check the sitemap's size or structure. These check limits are separate from your page slots.
Another scan is already running	Wait for it to finish and reload the list.
The selection or check result has changed	Close the dialog, refresh the list and select the required pages again.
The selection needs more page slots	Reduce the selection or free slots by disabling other pages.
The list looks empty	Check the combined filters and use Reset if needed.

A failed or incomplete scan does not overwrite a previous complete result. An existing, valid empty sitemap can, however, successfully return zero entries. Known project pages are retained in that case as well.

Check the effect in the app

After enabling a page, open a normal page on your website with the tracker installed. Check the project status and banner decision where applicable. In the app, check the same project under Content, with the matching date range and after refreshing the values.

If you expect individual analytics, check that the path is Active in page management. Earlier aggregate values are not redistributed afterwards. A recognised 404 page is not recorded as a normal request, even if it has a sitemap entry.

Read more: Content and page metrics, Install the tracking code and Troubleshooting.