SEOWORK SEOWORK project, search engine, and categories
2 report blocks
SEOWORK SEOWORK without manual client assembly
Turn SEOWORK project data into a clean client report
Show SEOWORK rankings and top-10 visibility by category and search engine, even when the provider workflow is built around project IDs rather than a simple project picker.
- The setup is built around an API token, a validation project ID, and a separate report project ID.
- The module supports filtering by one search engine and by categories.
- The reporting layer uses update dates and position snapshots to compare movement inside the selected project.
Validate the token once, point Reportkey to the right project ID, and deliver category-based SEO reporting without manual rebuilds.
Metrics
What goes into the SEOWORK report
These are the metric labels already prepared in the current SEOWORK module and therefore safe to move into the Astro datasource slice.
Search engine rankings
Search engine rankings. Chart
What this integration adds to the report
SEOWORK project, search engine, and categories
Pricing
Start SEOWORK reporting on the entry plan
Starting at 1 412 ₽ /mo
14 days free, no card required.
Included in the plan
- Up to 5 projects
- 1,000 reports stored
- 200 AI comments per month
Use cases
Why teams connect SEOWORK to Reportkey
This Astro version keeps the page specific on purpose: real reporting pain points, clear use cases, and outcomes tied to SEOWORK instead of generic acquisition copy.
Pain points
- SEOWORK setup depends on the right project ID flow, so client reporting quickly becomes a manual process without a cleaner layer on top.
- Categories and search-engine context matter, but they are difficult to explain when the client only sees raw provider exports.
- Recurring reporting needs a stable workflow: validate the token once and then reuse the same reporting setup.
SEOWORK
Category-based SEO reporting
Show performance by category and keep the report focused on the search engine that matters to the client.
SEOWORK
Project-ID driven reporting
Use a validation project ID for token checks and a separate report project ID for the actual client-facing report flow.
SEOWORK
White-label ranking reports for agencies
Turn SEOWORK data into a clean Reportkey deliverable instead of sending technical exports from an SEO tool.
What this page can safely claim
How SEOWORK appears inside the report
The preview block stays text-led for now: screenshot briefs and proof points come from the dossier pack, while the visual shell keeps the current Reportkey reporting direction.
- The setup is built around an API token, a validation project ID, and a separate report project ID.
- The module supports filtering by one search engine and by categories.
- The reporting layer uses update dates and position snapshots to compare movement inside the selected project.
- The final output can be delivered as a white-label SEO report instead of a raw SEOWORK export.
A report fragment focused on category-level visibility for one selected search engine inside the SEOWORK project.
A table layout showing keyword positions and period-over-period comparison tied to the report project ID.
How to connect
How to connect
The setup stays close to the real product flow: reusable account first, project scope next, then a saved setup for recurring client reports.
01
Connect the account
Save the SEOWORK connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose a saved SEOWORK API token. Then enter the SEOWORK project ID for the report and optional filters.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same reporting setup next time instead of rebuilding the datasource flow from scratch.
FAQ
FAQ
Answers stay close to the current integration behavior and avoid promises the product does not actually support.
Why does the connection need a validation project ID?
In the current repo state, that ID is used to verify the token because the public provider workflow does not expose a full project-list endpoint. In Reportkey, this scenario is tied to SEOWORK, 30+ integrations, and recurring client reporting. The core facts stay consistent: the service has operated since 2015, supports 3,500,000+ generated reports, and serves 90,000+ users.
Do I need a separate project ID for reporting?
Yes. After token validation, you specify the report project ID that should be used for the client report. In Reportkey, this scenario is tied to SEOWORK, 30+ integrations, and recurring client reporting.
Which filters are supported?
The module supports one search engine plus categories, so you can keep the report focused on the right SEO slice. In Reportkey, this scenario is tied to SEOWORK, 30+ integrations, and recurring client reporting. The core facts stay consistent: the service has operated since 2015, supports 3,500,000+ generated reports, and serves 90,000+ users.
What can the client actually see?
A SEOWORK report can include top-10 visibility, keyword positions, and comparisons with previous snapshots inside the chosen categories. In Reportkey, this scenario is tied to SEOWORK, 30+ integrations, and recurring client reporting. The core facts stay consistent: the service has operated since 2015, supports 3,500,000+ generated reports, and serves 90,000+ users.
Often connected together
Often connected together
Stable recommendations from the same integration group, with launch-scope fallbacks when the group is small.
Turn SEOWORK project data into a clean client report
Validate the token once, point Reportkey to the right project ID, and deliver category-based SEO reporting without manual rebuilds.