ScrepyDocs

Add a project

Add a website to Screpy for SEO audits, performance monitoring, and search visibility analysis.

Create one Screpy project for each website you want to monitor. A project is the home for your crawl data, technical SEO findings, Core Web Vitals, uptime checks, search visibility data, backlinks, reports, and team collaboration.

Use your canonical website domain when you set up a project. Screpy accepts a domain or full URL, then stores the root host for the project. For example, https://www.example.com/blog becomes example.com. Do not create separate projects for paths, landing pages, or individual articles on the same website.

Before you begin

Have these details ready:

  1. A clear project name, such as your brand or website name.
  2. The main domain you want Screpy to analyze.
  3. The primary country and language for the website.
  4. An estimate of how many URLs you want the first crawl to cover.

One project, one website

Use the main root domain without a path. Add a separate project only when you need to monitor a genuinely separate website or domain.

Create the project

Open the project switcher in the sidebar, then choose Add project. Enter a project name and the website's main domain. The domain must be reachable by Screpy and cannot already exist in your account.

The same project switcher lists the websites already in the workspace. Select one there whenever you need to change the active project; its dashboard, crawl data, search data, reports, and settings then become the views you are working with.

Next, choose the website's primary country and language. This keeps the project aligned with the market and audience you are trying to serve. You can update project settings later when your website, crawl scope, or monitoring needs change.

If you already use Google Search Console, the setup screen also offers an import option. Use it to bring an eligible site into Screpy, then continue with the same project and crawl setup.

Choose an initial crawl scope

During setup, choose the maximum number of URLs and crawl depth for the first analysis.

  • Max URLs controls how many pages Screpy can include in a crawl. Choose a scope that covers the area you want to improve without exceeding your available crawl capacity.
  • Depth controls how many link levels Screpy follows from the starting domain. A lower depth is useful for a focused section; a higher depth gives a broader view of a larger website.

You can refine crawl behavior later in Project settings, including whether crawling is enabled and how future analysis runs behave.

Allow Screpy to access your site

Screpy needs to reach public pages before it can analyze them. If your host, CDN, WAF, or firewall restricts automated traffic, allow the IP addresses shown in the project setup screen.

Your robots.txt rules must also allow Screpy's crawler. Keep your existing policies, but make sure they do not block ScrepyBot. A simple allowed rule looks like this:

User-agent: ScrepyBot
Allow: /

Access errors stop useful analysis

If Screpy cannot reach the domain, setup will show an error. Check DNS and server availability first, then review firewall rules and robots.txt before trying again.

What happens after setup

When the project is created, Screpy starts the first crawl and prepares the project for monitoring. It also creates the initial homepage Core Web Vitals record and starts uptime monitoring when it is enabled for the project.

The first completed crawl gives you the foundation for Quick Wins, Pages, Links, Images, and on-page SEO findings. Search visibility, backlink, and ranking widgets become useful as you connect their data sources or configure those features.

Common setup issues

IssueWhat to check
The domain cannot be addedUse the root domain, confirm it is publicly reachable, and check that it is not already in your account.
Screpy cannot access the siteAllow the setup-screen IP addresses in your firewall or WAF and permit ScrepyBot in robots.txt.
The project limit is reachedReview your Billing, plan & usage before adding another project.
The crawl scope is too smallAdjust URL capacity or depth in Project settings, then start a new crawl when you are ready.

Next steps

On this page