Content and engineering tickets are judged by what happens in Google Search, but the numbers live in Search Console. The GSC Wizard app for Jira puts clicks, impressions, CTR and average position next to the issue that changed the page, on a dashboard and in Rovo, compared with the previous period.
The app is read-only. It needs a GSC Wizard account with a plan or the 7-day trial.
The short answer
Jira has no built-in Search Console data. The GSC Wizard app adds it where the work is tracked: each issue lists the URLs it is about with their real search numbers, and the same figures are on a dashboard and one question away in Rovo.
A rewritten article, a new template or a redirect fix is closed in Jira, and whether it worked is found out somewhere else, if at all. I built the app so that the answer sits on the ticket.
Each issue carries the Search Console figures of the pages it is about, so a content or engineering ticket is reviewed with the result in view instead of a screenshot pasted into a comment.
Every figure comes with its change against the previous period, so you can see whether the pages moved after the work shipped.
Developers, writers and project managers read the data where they already work. The SEO tool stays with the people who configure it.
Four pieces, all read-only. The app never changes anything in GSC Wizard or in Search Console.
Add the URLs an issue is about, or let the panel pick them up from the summary and description, and see each URL’s clicks, impressions, CTR and average position for the last 7 days, 28 days, 3 months or 6 months next to the change from the period before. An issue tracks up to 25 URLs.
Details opens one URL with its daily clicks and impressions and the ten queries that bring the most clicks, against the previous period or the same period last year.
The GSC Wizard SEO analyst agent answers questions such as “how are the URLs in this issue doing in Google Search?” with the real numbers. From an issue it uses the tracked URLs; anywhere else you paste the URLs into the question.
It only repeats numbers the app returned and always says which period they cover. The action behind it can also be added to your own Rovo agents.
The same table for a fixed list of up to 25 URLs, on any Jira dashboard: launch pages, top landing pages, or the pages a team owns.
A Jira admin connects or disconnects the GSC Wizard account, sees which account and plan it is, and limits Jira to the Search Console properties they select.
Search Console data settles two to three days behind today, so every period ends three days ago. The comparison is the period of the same length directly before it: the last 28 days against the 28 days before.
Clicks and impressions change in percent. CTR changes in percentage points. Position is an average where lower is better, so an up arrow means the page moved up.
Search Console records every URL exactly, so the https, www and trailing-slash variants of a page are different URLs, and only the one Google indexed has data. A row marked No data usually has one of those differences.
A URL is read from a Domain property that covers its host when there is one, otherwise from the longest URL-prefix property it starts with. Discover, News and image search are not included.
You need Jira Cloud, a Jira administrator, and a GSC Wizard account with an active plan or trial and your Search Console properties connected and activated.
In GSC Wizard, open Account, then API keys, and create a key with Read only access. It is shown once.
A Jira administrator installs the app, following the install steps in the setup guide.
In Jira, open Apps, Manage apps, GSC Wizard, Configure. Paste the key, connect, then keep all active properties or select only the ones Jira users may read.
On an issue, add Search performance (GSC Wizard) from the Apps menu and paste the URLs the issue is about.
Every step, setting and error message is in the Jira setup guide. The dashboard gadget and the Rovo agent need no further setup.
The app asks Jira for three permissions and talks to one outside address.
storage:appKeeps the API key as an encrypted Forge secret, the property selection, and a cache of answers that expires after an hour (ten minutes for the property list).
read:jira-workReads the issue summary and description for URL suggestions and the issue’s tracked-URL list, and checks that the person on the admin page is a Jira administrator.
write:jira-workSaves the tracked-URL list on the issue. Nothing else is written.
The GSC Wizard REST API. The app sends it the page URLs being looked up and the date range, and it returns the metrics. GSC Wizard does not store the arguments of read requests.
The app stores no Atlassian account IDs, names or e-mail addresses. Disconnecting deletes the API key at once, and uninstalling the app removes its storage.
Every person signed in to the Jira site can look up URLs on the properties you allow, whether or not they can see a particular issue. If the connected account holds client or private properties, select only the ones that belong in this Jira site.
Calls count toward the connected account’s API rate limit, and the cache keeps a busy Jira site well inside it. Full detail is in the Privacy Policy. Questions go to support@gscwizard.com.
Yes, with the GSC Wizard app for Jira. Add the URLs an issue is about to the issue panel and you see each page’s Search Console clicks, impressions, CTR and average position for 7 days up to 6 months, with the change against the period before. The same numbers are available on a dashboard gadget and through a Rovo agent. A Jira administrator installs and connects the app; the setup guide has the current install steps.
Yes. The app adds a Rovo agent called GSC Wizard SEO analyst. From an issue it uses the issue’s tracked URLs, or the URLs in the description when none are tracked, and anywhere else you paste the URLs into your question. It only repeats numbers the app returned and says which period they cover. The action behind it, Get Google Search performance for URLs, can also be added to your own Rovo agents.
Jira Cloud, a Jira administrator to install and configure the app, and a GSC Wizard account with an active plan or trial. The Search Console properties you want in Jira must be connected and activated in GSC Wizard. The app reads its data through that account, so it stops working when the plan ends. GSC Wizard has a 7-day free trial; the pricing page lists the plans.
Every person signed in to the Jira site can look up URLs on the properties the administrator allows, whether or not they can see a particular issue. So if the connected GSC Wizard account holds client or private properties, select only the ones that belong in this Jira site. Anonymous visitors of public Jira projects never see data: the app refuses them. The URL list on an issue follows Jira’s own permissions: anyone who can view the issue sees it, and only people who can edit the issue can change it.
The app sends the page URLs being looked up, the date range and a read-only API key to the GSC Wizard REST API at mcp.gscwizard.com, and gets the metrics back. It sends no Atlassian user identifiers, issue keys or issue text other than the URLs. It stores no personal data: only the API key as an encrypted Forge secret, the property selection, and a cache of answers that expires after an hour. GSC Wizard does not store the arguments of read requests.
Search Console records every URL exactly, so https and http, www and no www, and a trailing slash or none are different pages. A row marked No data usually has one of those differences from the URL Google indexed. A row marked No property means no allowed property covers the URL: the property is not connected or activated in GSC Wizard, or the administrator did not select it for this Jira site.
It never changes anything in Search Console or in GSC Wizard. In Jira it writes one thing: the list of tracked URLs, saved as a property on the issue, which Jira lets only people with the Edit issues permission change. Nothing else is written.
Every setting, step and error message of the Jira app.
Scheduled Search Console reports and SEO alerts in the channels you choose.
The same reports and alerts as cards in a Teams channel.
SEO alerts as Linear issues in the team that fixes them.
Search Console numbers for the page behind every board item.
Search performance on the Asana task that works on a page.
All integrations are listed in the integrations documentation.
Start a GSC Wizard trial, connect your properties, and give your Jira site a read-only key.
Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.