Mattering Automations Google PageSpeed integration

Connect Google PageSpeed Insights to Mattering Automations: run full Lighthouse audits (performance, accessibility, best practices, SEO) as a scheduled workflow step.

Get the credential Connect Verify Node reference Troubleshooting

The Mattering Automations Google PageSpeed integration wraps the PageSpeed Insights API in a single focused node: give it a URL and a strategy (mobile or desktop) and it returns the full Lighthouse result, category scores included.

Setup is one Google Cloud API key, and the PageSpeed Insights API is free. On a schedule, this turns performance regressions into tracked work instead of something nobody notices until rankings slip.

Before you start

A Google Cloud project with the PageSpeed Insights API enabled.
A Mattering workspace with access to the Automations app.

Create or reuse a Google API key

The connector authenticates with a Google Cloud API key sent as a query parameter. One key serves every Google API-key integration on Mattering.

In the Google Cloud console, select your project and enable the PageSpeed Insights API (search for it in the API Library).

Open APIs and Services > Credentials and click Create credentials > API key, or reuse the key you already use for other Mattering Google integrations.

The PageSpeed Insights API is free from Google. One Google API key serves every Google API-key integration on Mattering; each API just needs enabling on the key's project.

Copy the key (it starts with AIza).

Connect Google PageSpeed to Mattering

In Mattering Automations, open Connectors and click Add Connector.

Choose Google PageSpeed Insights from the list.

Click Create new credential, paste the API key, and save. The credential is stored encrypted in Google Secret Manager.

Click Connect. The PageSpeed Analyze node appears in your canvas palette.

Verify it works

Open an automation canvas and drop PageSpeed Analyze onto it. Set url to any public page and strategy to mobile, then run a test step: a successful response returns the Lighthouse result with category scores for performance, accessibility, best practices, and SEO.

Node reference

1 node, generated from the connector itself so this reference always matches what ships.

Read and query nodes 1

PageSpeed Analyze

gapi_pagespeed_analyze

Run a Lighthouse PageSpeed Insights analysis for a URL (performance, accessibility, best practices, SEO, PWA).

Using the integration

On the automation canvas

Run audits on a weekly schedule and write the category scores into a Mattering database for a trend line. Branch on a score threshold to open a task when performance regresses, so a slowdown becomes assigned work the day it happens.

Any public URL

The API works on any publicly reachable page, so you can audit competitor pages alongside your own on the same schedule.

From AI assistants over MCP

The node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can pull an audit and read the specific failing Lighthouse checks before recommending fixes, instead of guessing.

Troubleshooting

The node cannot audit a page behind a login

PageSpeed Insights fetches the URL from Google's infrastructure, so only publicly reachable pages can be audited. Use a public URL or a preview URL that does not require authentication.

The node reports the API is not enabled

Enable the PageSpeed Insights API on the key's project in the Google Cloud API Library, and confirm the key's API restrictions include it.

Calls fail with a quota error

Google applies request quotas to keys. Google's documentation is the source of truth for current limits; scheduled auditing of a normal page set sits comfortably inside them, but tighten the schedule if you audit many URLs frequently.

The Google PageSpeed MCP

What connecting Google PageSpeed unlocks for AI agents and automations, with common uses and FAQs.

More guides

All Automations documentation

Every integration guide, plus how connectors, credentials, and workflows fit together.

Google PageSpeed is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.