PR-CY Technical site checks and search quality signals
PR-CY report: site health every month
Reportkey pulls site analysis results from PR-CY and turns them into a report section the client understands: how many checks passed, where the errors and warnings are, the site's Yandex SQI and what changed since the last report, with the date of every check.
Sign up, add your PR-CY API key and set the domain in a project. Your first report in 5 minutes.
- The PR-CY API key is entered once; the domain is set per project.
- Errors, warnings and passed checks with the date of every test.
- Tests that changed status since the last report, plus Yandex SQI.
TL;DR
PR-CY integration: enter the API key from the API tab of PR-CY account settings once on the integrations page, set the domain in a project, and a check summary, technical errors, Yandex SQI and period-over-period changes reach the client in a recurring report.
A technical site audit in every report
Technical problems rarely hit traffic straight away. A redirect broken by a release, a section blocked in the robots file by mistake, an expired certificate: they pile up quietly and then hurt rankings. A one-off audit at kickoff will not catch them. You need a regular check that both the specialist and the client can see.
PR-CY is a site analysis service that runs a set of tests against a domain and flags errors and warnings. Reportkey connects to its API and adds a site health section to the recurring report, sent as a link or PDF with traffic and rankings.
Connecting PR-CY: key and domain
You need an API key from the API tab in PR-CY account settings. Enter it once on the integrations page and set the client’s domain in each project. An agency with dozens of clients uses one key, and quota comes from the shared PR-CY account package. With a key PR-CY allows ten requests per minute plus a daily plan limit; Reportkey stays within it and retries when the service asks to wait.
PR-CY site analysis: check summary
The first block is a summary from the analysis card: passed tests, tests with warnings, tests with errors, when the analysis was last updated and whether it has expired. It is the short answer to “is the site all right?”
Technical checks: redirects, robots, sitemap, certificate
The second block is a detailed table of technical tests, each with name, status and date: server response and redirects, robots file, sitemap, certificate and other tests from the PR-CY catalogue. The test set is chosen per project, because an online store and a service site care about different checks.
Know the tool’s boundary. PR-CY tests the domain; it does not crawl every page. Broken links deep in the site, duplicates and template issues need a crawler. For regular control of the basics, the PR-CY set is enough.
Yandex SQI and search signals
The third block covers search signals, first of all Yandex SQI and its change. Clients often treat SQI as a final grade, so show it regularly and with a date: Yandex recalculates it on its own schedule, and the report value belongs to the PR-CY check day.
Changes since the last report
The block clients value most is what changed. The PR-CY API returns the latest snapshot rather than history, so Reportkey stores a snapshot at each build and compares it with the previous one. The report lists tests that switched status: what broke and what got fixed this month.
PR-CY next to search engine data
Search engines add their own view: indexing and crawl errors from Yandex Webmaster, coverage and clicks from Google Search Console and visits from Yandex Metrica. Rankings come from SE Ranking or Pixel Tools, competitive visibility from Keys.so. See all SEO integrations. AI insights and branding are not on every plan. Browse the SEO agency demo report and pricing.
Metrics
What goes into the PR-CY report
These are the metrics that the PR-CY integration already brings into Reportkey reports.
Site checks
Errors
Warnings
Yandex SQI
Last check date
What this integration adds to the report
Technical site checks and search quality signals
Pricing
PR-CY reporting: plans and free trial
14 days free, no card required. Prices and plan limits are on the pricing page.
Use cases
Why teams connect PR-CY to Reportkey
Real reporting jobs, typical pain points, and the outcomes teams get from PR-CY in client reports.
Pain points
- The technical audit happens once at kickoff, and later the client discovers a broken redirect or an expired certificate on their own.
- A PR-CY screenshot in the report does not show what changed since last month.
- The client cannot tell how fresh a check is and argues with numbers that are weeks old.
PR-CY
An SEO agency on a monthly retainer
Every monthly report has a site health section: how many checks passed, which errors appeared and which were fixed. The client sees the technical side is under control without commissioning a separate audit.
PR-CY
A web studio maintaining client sites
After each release the studio must confirm nothing broke: redirects, robots file, sitemap, certificate. The changes block lists tests that switched status, so a problem shows up before it hurts rankings.
PR-CY
A business owner who watches the site personally
The owner receives a short monthly report with Yandex SQI, error and warning counts and what changed. That is enough to decide whether to call the contractor.
Report preview
How PR-CY appears inside the report
The report keeps the familiar Reportkey layout: source sections and period comparison.
Three tiles for passed, warnings and errors, a technical check table with test name, status and date, a list of tests that changed status since the last report, and the SQI value with its change.
How to connect
Three steps to the first report
Connect the account once, choose the reporting scope, and save the setup for recurring client reports.
01
Connect the account
Save the PR-CY connection once so the same datasource can be reused across recurring client reports.
02
Choose the reporting scope
Choose the site from your PR-CY account that should supply search impressions, clicks, queries, and pages to the report.
03
Save the setup and generate the report
Keep the selected scope in the project and reuse the same report setup next time instead of connecting the source again.
FAQ
Frequently asked questions
Short answers about how the integration works in Reportkey today.
What do I need to connect PR-CY?
An API key from the API tab in PR-CY account settings, plus the project domain. Enter the key once on the Reportkey integrations page and set the domain in each project. Your remaining quota is shown in the Limits section of the PR-CY account.
Does PR-CY check every page of the site?
No. PR-CY analyses the domain with a set of tests: availability, redirects, robots file, sitemap, certificate and search signals. It is not a full crawl, so broken links on deep pages are better found with a dedicated crawler.
Where does the period comparison come from?
The PR-CY API returns the latest analysis snapshot with its update date and does not describe past snapshots. Reportkey saves a snapshot at every report build and compares the current response with the previous one, so the changes block appears from the second report onward.
How fresh are the results?
Each test has its own update date, shown next to the result. When an analysis is stale, Reportkey can trigger a recheck and wait for it to finish. A recheck uses PR-CY plan quota, so for monthly reporting refreshing once per period works well.
Why does Yandex SQI differ from what I saw in Yandex Webmaster?
PR-CY shows SQI as of its last check, while Yandex recalculates the index on its own schedule. If PR-CY checked the site before an SQI update, the values will differ. Rely on the check date printed in the block.
Related integrations
Often connected together
Working sources that teams usually add to the same report.
PR-CY report: site health every month
Sign up, add your PR-CY API key and set the domain in a project. Your first report in 5 minutes.