Skip to content

Website General Settings

Configure basic website information, authentication, and management options for individual websites in your Agora dashboard.

Overview

Website General settings are specific to each individual website and stored in your organization's database. These settings control how Agora interacts with and scans your website, including authentication requirements and basic website information.

Accessing Website General Settings

  1. From Dashboard: Navigate to any website in your dashboard
  2. Open Website View: Click on the website card to enter the website interface
  3. Navigate to Settings: Click the "Settings" tab in the website interface
  4. Select General Tab: Choose the "General" tab to access basic website settings

Website Information

Configure the basic details and metadata for your website.

Display Name

Purpose: Friendly name shown throughout the Agora interface

Best Practices:

  • Use a descriptive name that's easy to identify
  • Can be different from the actual domain name
  • Appears in reports, dashboard cards, and export files
  • Consider including environment (e.g., "Company Website - Production")

Examples:

  • "Marketing Website"
  • "E-commerce Store - Staging"
  • "Customer Portal"
  • "Documentation Site"

Sitemap URL (Optional)

Purpose: XML sitemap URL for automatic page discovery during scans

Configuration:

  • Must be from the same domain as the website
  • Should point to a valid XML sitemap
  • Automatically imports URLs when provided
  • Updates URL list when sitemap changes

Supported Formats:

  • Standard XML sitemaps (sitemap.xml)
  • Sitemap index files
  • Compressed sitemaps (sitemap.xml.gz)
  • Custom sitemap paths

Benefits:

  • Automatically discovers new pages
  • Ensures comprehensive website coverage
  • Reduces manual URL management
  • Keeps scan scope up-to-date

Authentication Settings

Configure authentication methods for websites that require login credentials or special access permissions.

Basic Authentication

Purpose: Configure HTTP Basic Auth credentials for protected websites

When to Use:

  • Development or staging environments with Basic Auth
  • Internal websites requiring simple authentication
  • Legacy systems using HTTP Basic Auth
  • Any site prompting for username/password in browser

Configuration:

  • Username: Your Basic Auth username
  • Password: Your Basic Auth password (stored securely)
  • Auto-apply: Credentials automatically used during scanning
  • Secure storage: Passwords encrypted and stored safely

Security Notes:

  • Credentials are encrypted in the local database
  • Only used for scanning purposes
  • Not shared between different websites
  • Can be updated or removed at any time

Advanced Authentication

For more complex authentication scenarios:

  • Session-based auth: Configure through browser simulation
  • Token-based auth: Set custom headers in scanning options
  • OAuth flows: Use browser-based authentication workflows
  • Custom headers: Add authentication headers as needed

Website Management

Scan Configuration

Control how Agora scans and interacts with your website:

Scan Depth

  • Configure how deep into the site structure to scan
  • Set maximum number of pages to discover
  • Control crawling behavior and scope

Custom Headers

  • Add custom HTTP headers for all requests
  • Include authentication tokens or API keys
  • Set user agent strings or custom identifiers

Crawling Rules

  • Define URL patterns to include or exclude
  • Set up crawling delays for rate-limiting
  • Configure JavaScript rendering requirements

Data Management

Scan History

  • View all previous scans for this website
  • Access historical scan results and trends
  • Compare scan results over time
  • Export historical data

URL Management

  • View all discovered URLs for the website
  • Manually add or remove specific URLs
  • Organize URLs using tags and filters
  • Track URL scan status and results

Danger Zone

Critical website management actions that cannot be undone.

Delete All URLs

Purpose: Permanently remove all URLs from the website while preserving website configuration

What Happens:

  • All URLs and their scan results are deleted
  • Website configuration and settings remain intact
  • Tags and integrations are preserved
  • Scan history is cleared

When to Use:

  • Starting fresh with a new URL set
  • Clearing old or outdated scan data
  • Preparing for a major website restructure
  • Removing test data after initial setup

Safety:

  • Requires confirmation dialog
  • Cannot be undone once confirmed
  • Consider exporting reports before deletion
  • Website itself remains in dashboard

Delete Website

Purpose: Permanently delete the entire website and all associated data

Access Requirements:

  • Admin or Power User permissions only
  • Organization-level permission required
  • Confirmation from authorized user

What Happens:

  • Website completely removed from dashboard
  • All URLs and scan results deleted
  • All tags and configurations removed
  • Integration settings and history cleared
  • Cannot be recovered after deletion

When to Use:

  • Website no longer needs monitoring
  • Cleaning up test or development sites
  • Removing duplicate website entries
  • Consolidating website management

Safety:

  • Multiple confirmation dialogs required
  • Requires elevated permissions
  • Cannot be undone under any circumstances
  • Export all critical data before deletion

Best Practices

Website Setup

  • Use descriptive names that clearly identify the website and environment
  • Configure authentication immediately if the website requires it
  • Add sitemap URLs for comprehensive automatic discovery
  • Test authentication by running a small scan first

Security Considerations

  • Limit Basic Auth scope to only websites that require it
  • Use strong passwords for Basic Auth configurations
  • Regular credential rotation for better security
  • Monitor access logs if your website provides them

Data Management

  • Regular cleanup of old or irrelevant URLs
  • Export reports before making major changes
  • Tag organization for easier URL management
  • Backup configurations before website restructures

Team Collaboration

  • Document authentication setup for team members
  • Share sitemap locations with content managers
  • Coordinate deletions with team leads
  • Use descriptive naming for team clarity