What is Google's Universal Cart, and what does it read from a shop?

Universal Cart is a shopping cart Google launched in the US on October 15, 2026, in Google Search and the Gemini app: a shopper saves products from many retailers in one place, Google watches them for price drops and restocks, and checkout runs through Google Pay or the merchant's own site. It draws on Google's Shopping Graph, which Google fills from Merchant Center feeds and from what shops publish on their own pages.

GuideBy clickdPublished Updated 11 minute read

  • October 15Launched in the US in 2026, in Search and the Gemini appFrom Google's launch post
  • 60 billion+Product listings in the Shopping Graph, continually refreshedGoogle's own figure, in its launch post
  • 3,808Online shops clickd has read, each at its latest read276,581 of their pages, as of November 1, 2026
  • 40%Of those shops have pages that nearly copy each otherPairs sharing half or more of their text, against 18% of every site

Counted from the 316,711 sites clickd has read, each at its latest read, as of November 1, 2026.

Check a product page

Type the address of one of your product pages. clickd reads its Product data as a crawler gets it, before any script runs, and holds it to the fields Google lists for merchant listings.

A worked exampleA real product page, as clickd checked it on October 17, 2026. Pages change, so check it again for today's answer.

Checkedallbirds.com/products/mens-tree-runnersRequired fields in place; 3 recommended to add or fix
Required
  • namePresent
  • hasVariantPresent
  • imagePresent
  • offersPresent
  • pricePresent
  • priceCurrencyPresent
Recommended
  • productGroupIDPresent
  • variesByPresent
  • availabilityPresent
  • itemConditionMissing
  • shippingDetailsMissing
  • hasMerchantReturnPolicyMissing
  • brandPresent
  • gtin, mpn or skuPresent
  • descriptionPresent
  • variant idPresent

Fix firstitemConditionSay whether it is new, refurbished or used, as https://schema.org/NewCondition.

Looks buyableA guessA button that says “Add to Cart - $100”, in the HTML before any script runs.

Every field the check read2 things, 17 fields

ProductGroupMen's Tree Runner

FieldNeedStateOn the pageWhat it means
nameRequiredPresentMen's Tree RunnerNames the product.
productGroupIDRecommendedPresentMENS_TREE_RUNNERSThe parent id the variants share.
variesByRecommendedPresentsize, colorWhat the variants differ by.
hasVariantRequiredPresent7 on this page, 42 elsewhereEach variant as a Product, and 42 on pages of their own, by address.

ProductMen's Tree Runner - Jet Black (White Sole) - Size 8

FieldNeedStateOn the pageWhat it means
nameRequiredPresentMen's Tree Runner - Jet Black (White Sole) - Size 8Names the product.
imageRequiredPresenthttps://www.allbirds.com/cdn/shop/files/TR3MJBW080_SHOE_LEF…, and 3 more4 images.
offersRequiredPresent1 OfferThe shop selling it.
priceRequiredPresent100A price above zero.
priceCurrencyRequiredPresentUSDA three-letter ISO 4217 code.
availabilityRecommendedPresentInStockA schema.org ItemAvailability.
itemConditionRecommendedMissingNothingSay whether it is new, refurbished or used, as https://schema.org/NewCondition.
shippingDetailsRecommendedMissingNothingAdd shippingDetails with the rate, where it ships and how long it takes, or set shipping in Merchant Center.
hasMerchantReturnPolicyRecommendedMissingNothingAdd the return policy the shop has: the countries it covers and its kind, or set returns in Merchant Center.
brandRecommendedPresentAllbirdsNames the brand.
gtin, mpn or skuRecommendedPresentsku: TR3MJBW080No GTIN, but an sku. Add the GTIN when the product has one.
descriptionRecommendedPresentThe Allbirds Tree Runner is a breathable and lightweight sn…Describes the product.
variant idRecommendedPresentTR3MJBW080Its own id.

The other six variants on the page, sizes 9 to 14, gave the same fields, each marked out of stock that day.

Free, one page at a time. It reads what the page publishes; Merchant Center and Google’s own review decide whether a product shows in Universal Cart.

What is Google's Universal Cart?

It is one cart for shopping across Google. Google's launch post, by Suresh Ganapathy, senior director of product management for consumer shopping, says a shopper can save products from several retailers in AI Mode in Search or in the Gemini app, and come back later to find them where they were left. Google first showed it at I/O on May 19, 2026.

Google's launch post says the cart does four things once a product is in it:

  • Watches each saved product for price drops and for when it is back in stock, from the Shopping Graph, which Google puts at more than 60 billion continually refreshed product listings.
  • Draws on Google Wallet, so it can weigh a shopper's card perks when suggesting how to pay, and shows promo codes in the cart.
  • Checks out in a few taps with Google Pay at many stores, or sends the items to the merchant's own cart to finish on the merchant's site.
  • Leaves the merchant as the seller of record, sending the order confirmation and giving customer support.

How Universal Cart works, as Google describes it

  1. A shopper savesProducts from several retailers, in AI Mode in Search or in the Gemini app
  2. Google watchesEach saved product, for price drops and for when it is back in stock
  3. The shopper checks outIn a few taps with Google Pay, or in the merchant's own cart
  4. The merchant sellsAs the seller of record, with the order confirmation and customer support
The Shopping GraphFeeds google watchesFilled from
  • Merchant Center feeds
  • What shops publish on their own pages

Where Universal Cart works, and where Google says it goes next

  1. May 19, 2026Shown at I/OGoogle first showed the cartI/O post
  2. October 15, 2026LiveLaunched in the USIn Google Search, AI Mode in Search and the Gemini appLaunch post
  3. In the coming monthsCheckout in Canada and AustraliaThen the UK, Google said in MayI/O post
  4. Later, with no dateYouTube and GmailGoogle said in May they would followI/O post
ComparedWhat Google has saidWhere
Where a shopper savesGoogle Search, AI Mode in Search, and the Gemini appLaunch post
Merchants named for checkoutNike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and many Shopify merchantsLaunch post
What checkout runs onThe Universal Commerce Protocol, an open standard Google co-developed with retailersLaunch post, I/O post

What does Universal Cart draw on?

Google names one source for the cart's prices and stock: the Shopping Graph. Google has described the Shopping Graph as its real time data set of the world's products and sellers, filled two ways: product data merchants send through Merchant Center, and what retailers and brands post across the web, including images, descriptions, reviews and videos.

For the part that comes from the web, Google's Search documentation is plain. Its guide to Product structured data recommends both structured data on the page and a Merchant Center feed, since providing both "maximizes your eligibility to experiences" and helps Google "correctly understand and verify your data". Some experiences combine the two: a product snippet may take its price from the feed when the page gives none.

What should a merchant do to take part?

There are two separate things to want, in this order. First, for a shopper to find a product on Google and save it; that rests on product data in the Shopping Graph, and any shop can work on it today. Second, for the shopper to pay inside Google; that rests on the Universal Commerce Protocol, and Google lets merchants in from a waitlist.

To be found and saved

Rests on product data in the Shopping Graph

Steps 1 to 4
  1. Send a Merchant Center feed

    Of your products, saying what the site says. Google recommends it alongside the data on each page, not in place of it.

  2. Put merchant listing data on each product page

    A Product with its name, image and offers, and an Offer with a price above zero and its currency. Each field is in the reference below. Only pages where a shopper can buy the product are eligible.

  3. Keep price, stock and pictures the same as the feed

    The cart's alerts are about price and stock, so those are the facts on a product page worth keeping exact.

  4. Let crawlers fetch and index each product page

    Not shut out in robots.txt, not marked noindex, and one canonical address for each product.

FromMerchant listing structured dataProduct structured data

To let shoppers check out on Google

Rests on the Universal Commerce Protocol, from a waitlist

Steps 5 to 10

The steps of Google's guide to the protocol for merchants, updated October 5, 2026, with what its Merchant Center steps ask for.

  1. Prepare Merchant Center and join the waitlist

    A Merchant Center account in good standing, with approved products for free listings. The guide links the waitlist from this step.

  2. Set return policies and a way to reach support

    Return policies in Merchant Center, each with the cost of a return, the window, and a link to the full policy, and at least one way to reach customer support.

  3. Mark which products can check out

    In the feed, native_commerce(checkout_eligibility) set to TRUE for each product to offer; missing or FALSE means it is not eligible. Product ids that match the checkout system, or a merchant_item_id that maps them, and a consumer_notice for products that need a legal or safety warning.

  4. Publish a profile for the protocol

    What the shop supports, for Google to read.

  5. Secure the endpoints

    Authenticated endpoints for Google to call.

  6. Choose checkout on Google or the shop's own cart

    Either the shopper pays on Google, or the cart passes to the merchant's own site to finish there. Google approves each integration before it goes live in AI Mode and the Gemini app.

Some products cannot use checkout on Google at all, the guide says, among them subscriptions, installment plans, personalized items, used and final sale items, pre-orders and goods that need an age check.

FromUniversal Commerce Protocol guidePrepare your Merchant Center account

The fields on each product pageAs Google lists them in Merchant listing structured data
FieldOnWhat it holds, with an example value
Required5 fieldsGoogle requires every one of these for a merchant listing.
nameProductThe name of the product, as the page shows it."Linen shirt"
imageProductThe address of a product photo a crawler may fetch.["https://acme.example/shirt.jpg"]
offersProductA nested Offer to sell the product.{ "@type": "Offer", … }
priceOfferThe current price, above zero.68.00
priceCurrencyOfferThe currency, as a three-letter ISO 4217 code."USD"
Recommended8 fieldsEach helps Google show the product. Give one only when the page shows it.
availabilityOfferWhether it can be bought now."https://schema.org/InStock"
itemConditionOfferNew, refurbished or used."https://schema.org/NewCondition"
shippingDetailsOfferThe shipping policy. Google recommends setting it once for the shop, on its Organization.{ "@type": "OfferShippingDetails", … }
hasMerchantReturnPolicyOfferThe return policy. Google recommends this once on the Organization too.{ "@type": "MerchantReturnPolicy", … }
brandProductAt most one brand, by name.{ "@type": "Brand", "name": "Acme" }
gtinProductThe barcode number, as digits. The most specific that applies."012345678905"
descriptionProductThe product description, which Google strongly recommends."A relaxed shirt in washed linen."
skuProductThe shop's own id for the product. One value."LS-NAT-M"

Google recommends more where they apply, such as color, size, aggregateRating and review. Give a rating or a review only when the page shows it.

Every field together, for a made up shop. Give only what your page shows.
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Linen shirt",
  "image": ["https://acme.example/images/linen-shirt.jpg"],
  "description": "A relaxed shirt in washed linen.",
  "brand": { "@type": "Brand", "name": "Acme" },
  "gtin": "012345678905",
  "sku": "LS-NAT-M",
  "offers": {
    "@type": "Offer",
    "url": "https://acme.example/products/linen-shirt",
    "price": 68.00,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition",
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": {
        "@type": "MonetaryAmount",
        "value": 0,
        "currency": "USD"
      },
      "shippingDestination": {
        "@type": "DefinedRegion",
        "addressCountry": "US"
      },
      "deliveryTime": {
        "@type": "ShippingDeliveryTime",
        "handlingTime": {
          "@type": "QuantitativeValue",
          "minValue": 0,
          "maxValue": 1,
          "unitCode": "DAY"
        },
        "transitTime": {
          "@type": "QuantitativeValue",
          "minValue": 2,
          "maxValue": 5,
          "unitCode": "DAY"
        }
      }
    },
    "hasMerchantReturnPolicy": {
      "@type": "MerchantReturnPolicy",
      "applicableCountry": "US",
      "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
      "merchantReturnDays": 30,
      "returnMethod": "https://schema.org/ReturnByMail",
      "returnFees": "https://schema.org/FreeReturn"
    }
  }
}
</script>

A checklist for your shop

  • Send Google a Merchant Center feed of your products that says what the site says.
  • Give each product page a Product with name, image and offers, and an Offer with a price above zero and its priceCurrency.
  • Add availability, shippingDetails, hasMerchantReturnPolicy, brand and a GTIN, from facts the page already shows.
  • Keep the price, stock and pictures on each page the same as in the feed.
  • Let crawlers fetch and index each product page: not shut out in robots.txt, not marked noindex, one canonical address.
  • Check a live product page from each template with the checker at the top of this guide.
  • To let shoppers check out on Google: set return policies and a way to reach support in Merchant Center, then join the waitlist.

What does clickd check on a shop's product pages?

clickd reads a shop's public pages the way a crawler does and holds each to its rulebook. These are the rules in it that bear on what Google reads from a shop's own pages. On the 3,808 online shops clickd has read, the markup mostly parses and the plain parts mostly do not hold: 68% of their pages carry structured data that parses, but only 40% have a description of a useful length and 53% describe every image.

Pages that pass, online shops against every site

What clickd checksShop pages passing, higher is betterEvery site's pages passingShop pages counted
Structured data that parsesEvery page, JSON-LD read as a search engine reads it68%63%250,049
Data of the right typeHome and offer pages, product pages among them80%84%116,513
One canonical addressEvery page85%79%250,049
The words in the HTMLHome, article and offer pages, before any script runs84%89%116,513
Images describedEvery page; one with no images passes53%54%250,049
A title of a useful lengthEvery page, 15 to 65 characters73%71%250,049
A description of a useful lengthEvery page, 70 to 165 characters40%44%250,049
Breadcrumb dataArticle and offer pages49%61%113,024
Ratings only with reviews shownEvery page96%97%250,049
Each a share of the pages that rule applies to. Counted over the 276,581 pages clickd has read on the 3,808 sites it has placed among online shops, each site at its latest read, as of November 1, 2026. A site read only in part speaks only for the pages read. The second column is the same rule over the 16,538,121 pages read on all 316,711 sites.
What clickd checks of the whole siteShops passingEvery site passing
Let crawlers in100%100%
Let AI crawlers in96%95%
Publish a sitemap74%67%
Settle on one address77%64%
No near copies among pages60%82%
Counted over the 3,808 sites clickd has placed among online shops, each at its latest read, as of November 1, 2026, against the 316,711 sites it has read in all.

40% of shops have pairs of pages sharing half or more of their text, against 18% of every site. On a shop that can be one page for each color or size of the same product. A score or a rule passed says pages are well formed. It does not say an assistant cites the site. Nor does it say Google will show a product in its cart.

See the online shops board for how shops rank against each other, and the rulebook for every rule above.

What does clickd not check?

  • Merchant Center, product feeds, or whether a feed agrees with the page. clickd reads only public pages.
  • The fields inside Product and Offer data, in the score. The rulebook checks that JSON-LD parses and that its type fits the page; it does not check price, currency, availability, shipping or returns, and no score counts them. The free schema markup checker does, one page at a time: each Product, ProductGroup and Offer field by field against the fields Google lists for merchant listings, and a guess from the HTML at whether a shopper can buy on the page.
  • Whether a product shows in Universal Cart, AI Mode or the Gemini app, or at what price. Nothing clickd reads can see that.
  • The Universal Commerce Protocol, checkout eligibility, or a merchant's profile for it.
  • Every product on a large shop. A read takes the first 100 pages unless more are asked for, and every figure counts only the pages read.
  • Product pages it cannot tell are product pages. clickd takes a page for an offer from its address, under /products/ or /services/, or from Product or Service data on it. A product page elsewhere with neither counts as an ordinary page, and the offer page rules do not reach it.

For what clickd does not check, Google's own Rich Results Test reads one page's Product data as Google does, and Merchant Center shows what it made of the feed and decides what is eligible.

How do you check a shop with your agent?

Connect your agent once over MCP (see connecting an agent), then work in the shop's own project so the agent can change what clickd finds. Ask for the plan, narrow it to the pages clickd takes for offers, fix one thing at a time in the template that makes them, and have clickd read the live shop again.

A sample session
> Use clickd to read yourshop.com and fix the product pages first.

mttr_plan({ site: "yourshop.com" })
  The fixes worth the most, in order, with their pages

mttr_pages({ site: "yourshop.com", kind: "service", failing: "structured-data" })
  The offer pages, product pages among them, with no structured data that parses

mttr_page({ site: "yourshop.com", path: "/products/linen-shirt" })
  One page: every rule it fails and the fix for each

> Deployed. Have clickd read it again and tell me what changed.

mttr_rescan({ site: "yourshop.com" })
mttr_changes({ site: "yourshop.com" })

For the shop's own repository there is a skill for your agent. It finds the product page templates, whether the shop runs on a Shopify theme, Next.js, WooCommerce or Magento, checks one live product page from each with mttr_product_check, fixes the data in the template, keeps it to what the page shows, deploys only as you allow, and checks again.

Version 2.1.0

Fixes the Product data in a shop's own product templates so it states what the page shows, and checks each live page with clickd before and after.

For Claude Code, from the top of the repository, on macOS or Linux

mkdir -p .claude/skills/clickd/references .claude/skills/clickd/references/shop-ready && curl -fsSL https://clickd.com/skills/clickd/SKILL.md -o .claude/skills/clickd/SKILL.md && curl -fsSL https://clickd.com/skills/clickd/references/tools.md -o .claude/skills/clickd/references/tools.md && curl -fsSL https://clickd.com/skills/clickd/references/workflows.md -o .claude/skills/clickd/references/workflows.md && curl -fsSL https://clickd.com/skills/clickd/references/reading-the-brief.md -o .claude/skills/clickd/references/reading-the-brief.md && curl -fsSL https://clickd.com/skills/clickd/references/confirming.md -o .claude/skills/clickd/references/confirming.md && curl -fsSL https://clickd.com/skills/clickd/references/shipping.md -o .claude/skills/clickd/references/shipping.md && curl -fsSL https://clickd.com/skills/clickd/references/troubleshooting.md -o .claude/skills/clickd/references/troubleshooting.md && curl -fsSL https://clickd.com/skills/clickd/references/after-a-rescan.md -o .claude/skills/clickd/references/after-a-rescan.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready.md -o .claude/skills/clickd/references/shop-ready.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/platforms.md -o .claude/skills/clickd/references/shop-ready/platforms.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/markup.md -o .claude/skills/clickd/references/shop-ready/markup.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/merchant-center.md -o .claude/skills/clickd/references/shop-ready/merchant-center.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/verify.md -o .claude/skills/clickd/references/shop-ready/verify.md

See the skill

For Codex, from the top of the repository, on macOS or Linux

mkdir -p .agents/skills/clickd/references .agents/skills/clickd/references/shop-ready && curl -fsSL https://clickd.com/skills/clickd/SKILL.md -o .agents/skills/clickd/SKILL.md && curl -fsSL https://clickd.com/skills/clickd/references/tools.md -o .agents/skills/clickd/references/tools.md && curl -fsSL https://clickd.com/skills/clickd/references/workflows.md -o .agents/skills/clickd/references/workflows.md && curl -fsSL https://clickd.com/skills/clickd/references/reading-the-brief.md -o .agents/skills/clickd/references/reading-the-brief.md && curl -fsSL https://clickd.com/skills/clickd/references/confirming.md -o .agents/skills/clickd/references/confirming.md && curl -fsSL https://clickd.com/skills/clickd/references/shipping.md -o .agents/skills/clickd/references/shipping.md && curl -fsSL https://clickd.com/skills/clickd/references/troubleshooting.md -o .agents/skills/clickd/references/troubleshooting.md && curl -fsSL https://clickd.com/skills/clickd/references/after-a-rescan.md -o .agents/skills/clickd/references/after-a-rescan.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready.md -o .agents/skills/clickd/references/shop-ready.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/platforms.md -o .agents/skills/clickd/references/shop-ready/platforms.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/markup.md -o .agents/skills/clickd/references/shop-ready/markup.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/merchant-center.md -o .agents/skills/clickd/references/shop-ready/merchant-center.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/verify.md -o .agents/skills/clickd/references/shop-ready/verify.md

See the skill

For Cursor, from the top of the repository, on macOS or Linux

mkdir -p .cursor/skills/clickd/references .cursor/skills/clickd/references/shop-ready && curl -fsSL https://clickd.com/skills/clickd/SKILL.md -o .cursor/skills/clickd/SKILL.md && curl -fsSL https://clickd.com/skills/clickd/references/tools.md -o .cursor/skills/clickd/references/tools.md && curl -fsSL https://clickd.com/skills/clickd/references/workflows.md -o .cursor/skills/clickd/references/workflows.md && curl -fsSL https://clickd.com/skills/clickd/references/reading-the-brief.md -o .cursor/skills/clickd/references/reading-the-brief.md && curl -fsSL https://clickd.com/skills/clickd/references/confirming.md -o .cursor/skills/clickd/references/confirming.md && curl -fsSL https://clickd.com/skills/clickd/references/shipping.md -o .cursor/skills/clickd/references/shipping.md && curl -fsSL https://clickd.com/skills/clickd/references/troubleshooting.md -o .cursor/skills/clickd/references/troubleshooting.md && curl -fsSL https://clickd.com/skills/clickd/references/after-a-rescan.md -o .cursor/skills/clickd/references/after-a-rescan.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready.md -o .cursor/skills/clickd/references/shop-ready.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/platforms.md -o .cursor/skills/clickd/references/shop-ready/platforms.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/markup.md -o .cursor/skills/clickd/references/shop-ready/markup.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/merchant-center.md -o .cursor/skills/clickd/references/shop-ready/merchant-center.md && curl -fsSL https://clickd.com/skills/clickd/references/shop-ready/verify.md -o .cursor/skills/clickd/references/shop-ready/verify.md

See the skill

An agent should add structured data only from facts already on the page: the price shown, the stock shown, the return policy the shop really has. Data that says more than the page does is a claim nobody checked, and a feed and a page that disagree give Google two answers to the same question.

What do people ask about Universal Cart?

Where does Universal Cart work?

In the US, from October 15, 2026, in Google Search, AI Mode in Search and the Gemini app. Google said in May that YouTube and Gmail would follow, with no date, and that checkout would come to Canada and Australia in the coming months, then the UK.

Who is the seller of record when a shopper checks out?

The merchant. Google's launch post says the merchant stays the seller of record, sends the order confirmation and gives customer support.

What product data does Google require on a product page?

For merchant listings, a Product with name, image and offers, and an Offer with a price above zero and its priceCurrency. Google recommends availability, shippingDetails, hasMerchantReturnPolicy, brand, a GTIN and more.

Does a shop need Merchant Center?

To be found, Google recommends a Merchant Center feed alongside the data on each page, not in place of it. To let shoppers check out on Google, its steps ask for a Merchant Center account in good standing, with approved products for free listings.

Which products cannot use checkout on Google?

Among others, Google's guide names subscriptions, installment plans, personalized items, used and final sale items, pre-orders and goods that need an age check.

How does the cart choose which seller to show?

Google has not said. Neither of its posts on Universal Cart describes how the cart picks a listing or a seller, or how it weighs a feed against a page.

Can clickd get a product into Universal Cart?

No. clickd reads a shop's public pages and checks their product data against the fields Google lists. Merchant Center and Google's own review decide whether a product shows in Universal Cart.

Sources

Google's announcements

Google's developer docs

Coverage

How the figures were counted. Every figure on this page is counted from the 316,711 sites clickd has read, each at its latest read, with drafts left out, as of November 1, 2026, and worked out again as sites are read. A share of pages counts only pages that were read: a site read only in part speaks for the pages read and no others. Each rule is the one in clickd's rulebook, decided by code. A score or a rule passed says pages are well formed. It does not say an assistant cites the site. The methodology explains each count.

Read next

Two guides that pick up where this one stops.

Every guide

Read your own site

Every rule in this guide, on your pages, with the fixes worth the most first. Free, about a minute.