← Back to priebera.sk
Portal Access

How the Remote Crawler Works

The remote crawler visits your published frontend pages the same way a real visitor would — loading each page in a real browser, waiting for dynamic content to render, and then analyzing it for accessibility issues.

IntroductionInstallationConfigurationRules ReferenceScanning LimitationsCLI & AutomationScheduler IntegrationLicence ActivationRemote CrawlerChangelogExtending AQG
On this page
OverviewHow Pages Are DiscoveredCookie Consent HandlingScreenshotsIssue HistoryWhat It Can and Cannot Scan
public
Rendered frontend scanning

The remote crawler uses a real browser context to analyze the rendered page output — not just raw backend fields. This helps detect issues caused by dynamic rendering, JavaScript components, third-party embeds, and frontend-only markup.

How pages are discovered

When you start a site scan, AQG fetches your sitemap to get the list of pages to scan.

If your site uses a sitemap index — a single /sitemap.xml that points to multiple sub-sitemaps — AQG automatically detects this and picks the correct pages sitemap. No manual configuration is needed.

If no sitemap is found, AQG falls back to crawl mode. It starts from your homepage and follows links to discover pages automatically.

For best results, make sure your TYPO3 site has a sitemap configured. Without a sitemap, page discovery depends on link crawling which may miss some pages.

For single-page scans, the exact URL you trigger from the backend module is used directly without any sitemap lookup.

Cookie consent handling

Many sites show a cookie consent banner before the content is accessible. The remote crawler handles this automatically by attempting to dismiss the banner before scanning the page.

This ensures that the actual page content — not just the consent overlay — is analyzed for accessibility issues. Cookie accept selectors can be configured in Remote Scan Access settings.

Screenshots

A screenshot is captured for each successfully scanned page. Screenshots are available in the Remote Page Detail view and in PDF exports.

Screenshots are automatically deleted after 30 days.

Issue history

Each scan is compared against the previous scan for the same site. New issues — found for the first time — and resolved issues — present before but no longer detected — are tracked separately.

This helps you focus on what changed since the last scan instead of reviewing the full issue set from scratch.

What the remote crawler can and cannot scan

The remote crawler scans published, publicly accessible pages — pages that are visible to real visitors.

Supported Not scanned
Publicly reachable pages TYPO3 backend-only drafts
Public language variants Password-protected pages unless access is configured
Pages accessible through configured scanner access/token if enabled Logged-in-only pages unless access is configured
Third-party embeds visible in the frontend PDF/document accessibility

Use the local backend scan for hidden or draft TYPO3 pages that are not yet publicly available.