Creating a Site Audit Project

To begin auditing a web page, you must create a Site Audit Project. A project defines the target URL and holds all historical runs, schedules, metrics, and generated artifacts.

Before you start

• Ensure the target URL is fully public and accessible without credentials.
• Ensure the target uses standard HTTP (80) or HTTPS (443) ports.
• Identify the target URL's final destination. If the URL performs redirects, enter the final destination URL directly to avoid routing delays.

Steps

To create a new project:

1. In the navigation sidebar, go to Site Audit.
2. Select New Project (or Create project if your dashboard is empty).
3. Fill in the project configuration fields:
   • Name: A descriptive label for the workspace (e.g., Corporate Homepage).
   • Slug: A URL-safe identifier automatically generated from the name, or customized to your preference (e.g., corporate-homepage). Must contain only letters, numbers, and hyphens.
   • Description: An optional summary of what this project monitors.
   • Target URL: The absolute URL to inspect (must start with http:// or https://).
   • Link to Resource: Optionally connect this audit project to an existing user-owned resource:
     • Static Site: Link to one of your Mincemeat Static Sites.
     • Instance: Link to one of your assigned Mincemeat Cloud Instances.
   • Tags: Optional comma-separated tags to filter and group projects in your dashboard (e.g., production, marketing).
   • Default Run Type: Select FULL (recommended for tracking Site Readiness Scores) or choose FAST, STANDARD, or CUSTOM depending on your needs.
4. Select Create Project.

What happens next

Upon creation, Mincemeat initializes the project workspace and performs a validation check on the target URL.

• The project dashboard displays a Pending first run state.
• Select Run Audit to manually trigger the first execution.
• If you linked the project to a static site, a shortcut button will appear, letting you quickly navigate between your deployment settings and audit history.

Troubleshooting

Problem	Possible cause	What to do
Target URL is rejected	URL is malformed, uses an unsupported port, or contains internal address space.	Verify the URL starts with http:// or https:// and resolves to a public endpoint. Read URL limits for more details.
Slug is already taken	Project slugs must be unique within your account.	Choose a different slug or add a unique suffix (e.g., -v2 or -prod).
Linked resource not showing	The static site or instance is owned by another user or has not been assigned to your role.	Verify resource ownership under the main dashboard before linking.