Project settings
Configure a Screpy project's market, crawls, tracking, uptime, and alerts.
Project settings define how Screpy understands and analyzes a website. Use them to keep the project aligned with the site you actually want to monitor, not as a substitute for fixing crawl access or page-level problems. Changes are saved together with Save settings and affect future monitoring or analysis.
Check the project identity first
Confirm the project name, domain, primary country, language, and reporting timezone before changing crawl behavior. A project should represent one website or root domain. Creating separate projects for individual paths or articles makes reporting and crawl history harder to interpret unless those paths are genuinely separate sites.
Configure search tracking
Set the refresh frequency for both Rank Tracker and Map Tracker. The available choices are Daily, Weekly, Every 2 weeks, and Monthly. Use a frequency that matches the project’s needs and available plan capacity; a daily setting is not useful when no one will review the result.
For Map Tracker, use Matching filters to define how new keywords find the intended business listing. Add a rule based on a listing’s website domain or title when a local result could otherwise match the wrong business.
Adjust crawl scope deliberately
The Crawler section controls whether crawling is enabled, its maximum URLs, depth, and JavaScript rendering. Advanced crawling exposes concurrency and delay controls. Start with a scope that covers the part of the site you need to improve. Increase it only when the current crawl cannot answer the question, such as when important sections are beyond the selected depth.
JavaScript rendering makes analyses substantially slower. Enable it only when important content is generated client-side and cannot be evaluated reliably without rendering.
Changes to settings affect future analysis. Keep the completed crawl that led to the decision as a baseline, update the setting, then run another crawl and compare the results. Do not expect a completed snapshot to change retroactively.
Configure availability alerts
The Uptime section enables availability checks for the project domain and sets the check interval in minutes. The Notifications section provides the email address for project alerts. Use a monitored public domain and an inbox that is actively watched; a private route or an unmonitored inbox defeats the purpose of alerting.
Delete a project with care
The Delete project control removes the project from the workspace. Screpy indicates that historical data remains system-restorable, but deletion still removes the project from normal workspace use. Confirm the exact project before proceeding and export reports or records that the team must retain.
Troubleshoot unexpected results
If the crawler cannot reach expected pages, inspect public access, redirects, robots.txt, and firewall or WAF rules before raising the crawl scope. More URLs do not solve a blocked or inaccessible site.