Jira integration

SEO reporting data in Jira

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 GSC Wizard issue panel in Jira listing three gscwizard.com URLs with clicks, impressions, CTR and average position and their change from the previous 28 days
The issue panel on a Jira Service Management request: three tracked URLs against the previous 28 days (example data).

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.

  1. Connect it once. A Jira admin pastes a read-only GSC Wizard API key and chooses which properties Jira users may read.
  2. Add the URLs. On an issue, add the pages it is about, or track the ones the panel finds in the description.
  3. Read the change. See clicks, impressions, CTR and position against the previous period, or ask the Rovo agent.
Why in Jira

Tickets judged on real search numbers

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.

The numbers sit 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.

Change, not just totals

Every figure comes with its change against the previous period, so you can see whether the pages moved after the work shipped.

No SEO tool login needed

Developers, writers and project managers read the data where they already work. The SEO tool stays with the people who configure it.

What the app adds

An issue panel, a gadget, a Rovo agent and an admin page

Four pieces, all read-only. The app never changes anything in GSC Wizard or in Search Console.

Issue panel

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 Details view of the GSC Wizard Jira app for one URL: period and comparison selectors, clicks, impressions, CTR and position with their change, daily charts with the previous period as a second line, and top queries
Details for one URL: last 28 days against the period before.
The GSC Wizard SEO analyst agent in Rovo on a Jira request, reporting clicks, impressions, CTR and position for the page in the description and its top queries
The GSC Wizard SEO analyst answering on a request about a page that lost traffic.

Rovo agent

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.

Dashboard gadget

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.

Admin page

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.

Reading the numbers

What the periods and changes mean

Periods end three days ago

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.

Changes

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.

Exact URLs

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.

Web search only

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.

Setup

Connected by an admin in a few steps

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.

1

Create a read-only key

In GSC Wizard, open Account, then API keys, and create a key with Read only access. It is shown once.

2

Install the app

A Jira administrator installs the app, following the install steps in the setup guide.

3

Connect and choose properties

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.

4

Add the issue panel

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.

Permissions and data

What the app can do in Jira, and what leaves it

The app asks Jira for three permissions and talks to one outside address.

storage:app

Keeps 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-work

Reads 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-work

Saves the tracked-URL list on the issue. Nothing else is written.

mcp.gscwizard.com

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.

No personal data stored

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.

Choose the allowed properties with care

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.

Frequently asked questions

Can I see Google Search Console data in Jira?

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.

Can I ask Rovo about Search Console data?

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.

What do I need before I install it?

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.

Who in my Jira site can see the search data?

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.

What leaves Jira, and what does the app store?

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.

Why does a URL show no data?

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.

Does the app change anything in Jira or Search Console?

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.

Same data, other tools

More ways to get Search Console data to your team

All integrations are listed in the integrations documentation.

Put Search Console numbers on the Jira issue that changed the page

Start a GSC Wizard trial, connect your properties, and give your Jira site a read-only key.

Search Console tips in your inbox

Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.