Scan profiles

Scan profiles are targeted configurations for recurring or manual checks. They define which URLs (from the sitemap and added manually) are processed with which scan type, which batch size and which schedule.

Profile overview

• Every profile belongs to a project and refers to the sitemaps or URL sets stored there.
• You can create multiple profiles per project, e.g. for different sections or frequencies.

URL selection from the sitemap tree

• Navigate through the sitemap tree and select the URLs or branches this profile should cover.
• URLs that are not selected will not be scanned by this profile.

Manual URLs

• Add manual URLs if individual pages are not part of the sitemap or should be checked in addition on purpose.
• Make sure to enter full paths and the correct scheme (http/https) so you don't trigger false matches.

Automation

• Use a cron expression to define when and how often a scan profile is run automatically (e.g. daily, weekly).
• Once configured, scans start fully automatically at the defined time - no manual intervention is needed.

Batch size

• The batch size limits how many URLs are processed per run or per sub-job.
• Smaller batches spread load and token usage more evenly; larger batches can be more efficient on stable sites.

Scan type

When you create a profile you choose the desired scan type:

• Spell check - AI-assisted check for spelling, grammar, typos and punctuation. Token cost depends on the text volume of the checked pages.
• Content assessment - rule-based check for test content, placeholder text, and suspicious URL patterns. Flat cost of 5 tokens per URL, which makes it especially cheap for recurring checks.
• Link check - rule-based check of every outgoing link for reachability, redirect chains, and mixed content. Costs 3 tokens per source page plus 1 token per 50 additional outlinks. See Link Check for details.

The scan type is set per profile and cannot be changed after creation. If needed, create separate profiles for spell check, content assessment, and link check to use all check types.

Tip: combine all three scan types for comprehensive quality assurance - spell check for linguistic correctness, content assessment for structural issues in your own content, and link check for the quality of outgoing links.

Archive unused profiles

• Archive profiles you no longer actively use to keep lists clean.
• Archived profiles generally don't start any new runs; the existing history stays viewable depending on the product.

Check dependencies

• A profile without a valid sitemap analysis or without a matching project URL doesn't deliver meaningful runs.
• When URLs disappear from the tree (404 in the source), update the sitemap and the selection in the profile.

Roles and permissions

• Depending on the workspace, only certain roles may create or archive profiles; missing buttons indicate missing permissions.

Notes

• Adapt automation and batch size to the size of the site and to your token budget.
• After changes to the sitemap check whether the URL selection in the profile is still correct.
• After creation, run one manual scan once before enabling a frequent automation.