SEO Project Workspace

Give each website its own SEO project. Switch between client sites, configure crawling and monitoring, connect the right data sources and work with your team without mixing website histories.

Create a project View pricing
Screpy project overview with the selected website's on-page audit, health trend, and connected SEO modules
Uber logo in Screpy SEO platform customer trust section
Philips logo in Screpy SEO platform customer trust section
FedEx Express logo in Screpy SEO platform customer trust section
Bosch logo in Screpy SEO platform customer trust section
Champion logo in Screpy SEO platform customer trust section
Iconfinder logo in Screpy SEO platform customer trust section
T-Mobile logo in Screpy SEO platform customer trust section
Carrefour logo in Screpy SEO platform customer trust section
Stanley logo in Screpy SEO platform customer trust section
Skoda logo in Screpy SEO platform customer trust section

Create Website Projects

Start with a recognizable project name and a reachable public domain such as example.com. Choose the country, language and initial crawl scope before beginning your website analysis.

  • Use a hostname, not an article, category or login-page path.
  • Choose Max URLs, crawl depth and JavaScript rendering during setup.
  • Check project capacity and Website Audit access in your plan.

Import Search Console Projects

Already manage websites in Google Search Console? Connect your Google account, select the available domains and add them as Screpy projects instead of entering each website manually.

  • Import only properties available to your authorized Google account.
  • Select the domains you want; matching properties are grouped by domain.
  • Import runs in the background; wait for projects to appear before continuing.

Review Multiple SEO Projects

Use the projects list to find the website that needs attention, then open its dashboard or a specific module. Owned and shared projects stay accessible without combining their analysis histories.

  • Review health and issue counts from the latest successful completed crawl.
  • Check available 30-day uptime and tracked-keyword counts per website.
  • Open Search Console, uptime, rankings, Core Web Vitals, backlinks or crawler tabs.
  • Confirm the selected project before changing settings or preparing a report.

Set Project Search Markets

Keep the project name, primary country, language and timezone aligned with the website you manage. These settings provide project context; they do not translate the website or set every keyword's individual search location.

  • Update the project name, country, language and timezone in Settings.
  • Review target location and device separately when adding tracked keywords.
  • The project domain is fixed after creation; a different hostname needs a new project.

Configure Website Crawl Scope

Adjust how a future crawl discovers and analyzes the website. Change the setting that addresses the actual problem, then inspect a new completed crawl rather than expecting old audit data to change.

  • Set Max URLs within available capacity and depth for link discovery.
  • Enable JavaScript only when essential content depends on client-side rendering.
  • Control following links, external links, image connections and link connections.
  • Adjust concurrency and delay for server capacity; these controls do not remove access blocks.

Schedule Website Monitoring

Different signals need different refresh schedules. Configure the supported monitoring settings for this project instead of treating a full crawl, ranking update and availability check as the same task.

  • Set ranking frequency and available time, weekday or month-day options.
  • Choose Maps frequency and business-matching rules for local tracking.
  • Configure AI Visibility frequency and supported platforms when your project has access.
  • Enable uptime checks and set their interval separately; options depend on project eligibility.

Connect Project Data Sources

Match external data to the correct website. Search Console and Cloudflare connections provide different evidence, and a project membership does not automatically authorize another person's external account.

  • Select an available Search Console property for the project.
  • Cloudflare analytics requires your authorized connection and a matching project zone.
  • Check connection, permissions and available data before interpreting an empty widget.

Manage SEO Team Access

Project owners add collaborators to the selected website with owner or member roles. Each person signs in with their own account and works with the project's data instead of sharing an owner's login.

  • Add an existing Screpy account by email; a new account requires a password in this flow.
  • Review names, email addresses, roles and join dates in the member table.
  • Owners manage membership; removing a person withdraws access to that project.
  • Owner/member roles are not custom, module-level or read-only client permissions.

Configure Alerts and Outreach Email

Send project alerts to the right recipient and configure outreach delivery separately. The project owner manages SMTP settings; setting a notification email does not schedule client reports.

  • Set the project's notification email for its alerts.
  • Owners configure the outreach mail server and sender identity.
  • Use Save and test, and resolve a failed email test before sending outreach.

Share Project SEO Reports

Prepare an update from the selected website's available data. Use your report templates and generate a PDF snapshot for people who need the findings without ongoing dashboard access.

  • Select report sections and branding supported by your plan.
  • Inspect source-specific periods and available records in the preview.
  • Generate the PDF on demand; templates do not automatically email recurring reports.

Talk about Project Workspace. With SEO MCP.

Connect an AI assistant to your Screpy project through SEO MCP. Select a project, review its overview and investigate supported crawl, ranking and search data using scoped access.

  1. Screpy: Hello! Let’s look at Project Workspace for example.com. What would you like to know?
  2. You: List my Screpy projects and open the overview for example.com.
  3. Screpy: Select example.com, then review its latest completed crawl and available project data. Your assistant only accesses projects your Screpy account can access. Project context: Project: example.com. Crawl: Latest completed run.
  4. You: Turn that into a short action plan.
  5. Screpy: I’ll keep the evidence and recommendations separate. Review the findings, choose one change and check the results afterward. Your next steps: Review: Check the source and date of each finding.. Decide: Choose the first change to make.. Verify: Compare the results after the change..
  6. You: Can you explain the evidence in plain language?
  7. Screpy: Yes. Ask about a supported result and I can explain what it shows, where it comes from and what is still uncertain. Missing data stays unavailable; recommendations are not automatic fixes.

Screpy documentation

Configure your Screpy project

Follow the setup and settings guides to choose a public domain, adjust crawling and configure project monitoring.

Read the Project Settings guide

SEO Project Workspace FAQ

Answers about website scope, setup, historical data, access and sharing.

Who can delete a project?

A project owner can confirm deletion in Settings. The project is removed from normal workspace use. Keep any needed reports first; there is no self-service restore workflow promised here.

What is an SEO project workspace?

A Screpy project groups one website's settings, crawl history, monitoring and reports. The workspace helps you choose the correct website and share its SEO context with authorized teammates.

Why is a dashboard widget missing data?

The module may need a completed analysis, tracked keywords, an eligible plan or an authorized connection. Check its actual availability; missing data is not a zero score or proof that the website has no activity.

Do new settings change previous crawl results?

No. Saved crawl settings apply to future analyses. Run a new crawl and compare completed results; changing capacity or rendering does not rewrite a historical snapshot.

Can an AI assistant manage my project through SEO MCP?

Yes. Supported MCP tools can list accessible projects, read project context and make explicitly requested settings changes. Creation and deletion require confirmation; deletion is owner-only. MCP access does not bypass plan or project permissions.

Does adding a teammate connect all external data for them?

No. Project access and external authorization are separate. Search Console uses the appropriate account/property connection, while Cloudflare analytics requires the viewer's authorized connection and matching website zone.

Can I change a project's domain?

The supported settings do not change the domain after creation. Create a new project for a different hostname; keep needed reports from the old project and do not assume its history transfers.

Which tools use the selected project?

Audits, crawling, rankings, Maps, AI Visibility, backlinks, search data, analytics, content and reports use project context. Each feature still needs its own eligible plan, setup or connection.

Can I manage multiple websites in Screpy?

Yes. Create a separate project for each website and switch between accessible projects. Check your plan's project allowance and the capacities needed for each monitoring feature before adding more sites.

Can agencies keep clients in separate projects?

Yes. Separate projects keep client histories, crawl settings, collaborators and reports distinct. Project membership grants product access; use a PDF report when a client only needs an update.

Do I need to add a client as a member to share a report?

No. You can generate a PDF report and share that document yourself. Add a member only when they need ongoing project access; membership is not a dedicated read-only report role.