Works with your stack.

What Qotler uses it for

Finding search opportunities from your real numbers: pages losing clicks, pages almost on page one, pages seen but rarely clicked, and two of your pages competing for one search. Checking whether Google has re-read a changed page, and measuring before and after.

Permission, in plain words

"View Search Console data for your verified sites." That's Google's read-only Search Console permission. Qotler can't add or remove users, submit sitemaps, request removals or change any setting.

Data read

For the one site you pick: clicks, impressions, click rate and average position, by day, by search and by page; the previous 28 days for comparison; and Google's index status for pages Qotler is tracking. Up to 90 days of history on first sync.

Set up

1. Settings → Connect Google
2. Approve read-only access on Google's screen
3. Pick your site from the list (your own site is shown first)

Good to know

Google publishes search data about three days late, so the newest days are always a little behind. If the site you pick doesn't match your workspace's website, the picker says so.

Disconnect

Settings → Disconnect Google. Qotler stops reading at once and deletes the Search Console and Analytics numbers it synced. You can also revoke access from your Google account; Qotler then stops using the data until you reconnect or disconnect.

What Qotler uses it for

Knowing which pages bring visits and key events, so experts focus on pages that matter to your business, not just pages with the most impressions. Grounding goals in your real numbers.

Permission, in plain words

"See your Google Analytics data." That's Google's read-only Analytics permission. Qotler can't edit properties, users, conversions, audiences or tags.

Data read

For the one property you pick: sessions, users, page views and key events by day, and broken down by channel, source and medium, landing page and event name. Current to yesterday. Up to 90 days of history on first sync.

Set up

1. Uses the same Google connection as Search Console
2. Pick your GA4 property
3. Numbers start syncing straight away

Good to know

Don't use Analytics? Choose "Don't use Google Analytics". Its numbers are cleared and Search Console carries on untouched. Changing the property only re-syncs Analytics.

Disconnect

Choose "Don't use Google Analytics" to stop just this source, or disconnect Google to stop both. Synced numbers are deleted either way.

What Qotler uses it for

Finding the speed fixes that matter most on your important pages, explaining them in plain words, and re-testing straight after a fix ships.

Permission, in plain words

None. Qotler asks Google's public PageSpeed Insights service to test your public pages, the same test anyone can run on any website.

Data read

Lighthouse scores for performance, accessibility, best practices and SEO; lab timings (first and largest contentful paint, total blocking time, layout shift, speed index); and real-user Core Web Vitals from Chrome when Google has enough visits to report them. The five biggest savings per page.

Set up

1. Nothing to connect
2. Switch on weekly speed tests in Settings, if you want them

Good to know

Each test takes Google 25 to 85 seconds, so results arrive a minute or two after a run starts. Smaller sites often have no real-user data yet; Qotler says so rather than guessing.

Turn off

Switch off weekly speed tests in Settings. Past reports stay in your dashboards.

What Qotler uses it for

When your site is built from code, Coding turns an approved fix into one small pull request: what changed, why, and the evidence behind it. Your team reviews and merges it like any other change.

Permission, in plain words

Access to the repository you choose. Qotler reads the code it needs, creates a branch for the fix and opens a pull request. It doesn't merge, and it doesn't work in repositories you didn't choose.

Data read

The files needed to make the approved change, such as a page template or layout. Your design guide in Mind tells Coding how the change should look.

Set up

1. Install the Qotler GitHub app
2. Choose the one repository for your website
3. Approve a fix to get your first pull request

Good to know

Every pull request is small and does one thing, so it's easy to review. Merging is always a human decision.

Disconnect

Uninstall the Qotler app from your GitHub settings, or remove the repository from its access list. Open pull requests stay in your repository for you to close or merge.

What Qotler uses it for

Applying approved changes to your posts and pages, like a new title, description or page copy, without copy and paste. Then reading the live page to confirm it worked.

Permission, in plain words

Permission to edit posts and pages on your site. Qotler only uses it for a change you approved, one change at a time.

Data read

The post or page being changed, so the "before" can be kept and the change can be checked. Your public pages are read the same way as for any site.

Set up

1. Connect your WordPress site
2. Approve a fix
3. Qotler applies it and checks it went live

Good to know

Connect with an account that can edit posts and pages, ideally one used only for Qotler, so you can see its changes in your revision history and remove it separately.

Disconnect

Disconnect in Qotler's Settings, or remove the access from your WordPress users screen. WordPress keeps its own revision history of every change.