C

Hard for AI agents to use

Speed: Fail (real visitors, last 28 days)

85

Find

Does your site let search engines and assistants read and list your pages?

25% of your grade · 7 of 11 goals pass

  • Titles and descriptions fit in a search resultFail

    2 of the 2 audits in this goal fall short: The title is 621 pixels wide; search results show about 600, so the end is cut and The description is 276 characters; search results show about 155, so the end is cut. Google sets no length limit and cuts a title or description to the device's width. SEO tools measure a title in pixels, since 60 characters run from 267 to 1,133 pixels, and count a description in characters. A cut loses the last words.

    • 621 pixels wide: https://www.relatedrentals.com/
    • 276 characters: https://www.relatedrentals.com/

    What to do Ask the people who run your site to keep each title short enough to show in full and each description to one or two sentences, with the words that matter first.

    For your web team: Keep each <title> within about 560 pixels of Arial at 20px, which is about 60 characters of ordinary text and fewer with wide capitals, with the main words first. Keep each meta description to 70 to 155 characters.

    Influencing Title Links in Google Search, Google
  • Your pages are listed in a sitemapPartial

    https://www.relatedrentals.com/sitemap.xml is a sitemap, and robots.txt does not name it. Google and Bing use an XML sitemap named in robots.txt to find your pages, and neither promises to index every page in it. A page must be indexed to appear in Google's AI answers.

    • No Sitemap line naming the sitemap: https://www.relatedrentals.com/robots.txt

    What to do Ask the people who run your site to publish a sitemap and to name it in robots.txt.

    For your web team: Serve a sitemap.xml (a urlset, or a sitemapindex for several files) and add a Sitemap line with the sitemap's full address to robots.txt.

    Build and submit a sitemap, Google
  • Every page has its own titlePartial

    The title is the page's own and repeats its words or lists search terms. Google builds the title link in search results from the page's title, and may change one that is missing, vague, boilerplate or repeated. A title of its own keeps your wording in front of searchers.

    • Related Rentals - Luxury Apartments in NYC, CHI, DC, SF, LA & BOS: https://www.relatedrentals.com/

    What to do Ask the people who run your site to give every page its own title that says what the page is and what it offers.

    For your web team: Add a <title> element to the head of every page. Describe that page in plain words as a phrase a person would read, and make it differ from every other page's title.

    Influencing Title Links in Google Search, Google
  • A shared link shows a previewPartial

    The page lacks og:title, og:description, and og:image. Open Graph tags decide the title, description and image a link shows when shared; Google shows your icon in results.

    • No og:title: https://www.relatedrentals.com/
    • No og:description: https://www.relatedrentals.com/
    • No og:image: https://www.relatedrentals.com/

    What to do Ask the people who run your site to set a share title, description and image for each page, and a site icon.

    For your web team: Add og:title, og:description and og:image meta tags to the head of each page, and a <link rel="icon"> that points to your icon.

    The Open Graph protocol, ogp.me
  • Search engines and AI assistants are allowed to read your sitePass

    Every AI search crawler and agent we grade is allowed. Training crawlers are allowed. A crawler is a robot that reads sites for a search engine or assistant, and one that is blocked cannot recommend you. Bing lists blocking Bingbot among the things to avoid, because content it cannot crawl may not be indexed or used in Copilot's answers.

    Overview of OpenAI crawlers, OpenAI
  • Search engines may list each pagePass

    The page answers, no tag or header keeps it out of search results, and robots.txt lets search crawlers read it. Google leaves out a page marked noindex, and a page its crawler cannot read cannot be listed or used as a supporting link in its AI features.

    AI features and your website, Google
  • Search results can show your pages' wordsPass

    All 2 audits in this goal pass. A page whose text is kept out of results leaves a search engine or assistant nothing to quote. Google's AI features follow nosnippet and max-snippet, and Bing keeps content marked noarchive out of Copilot and limits nocache pages to their address, title and snippet.

    Robots.txt Introduction and Guide, Google
  • Pages that do not exist say soPass

    A page that does not exist answers 404. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

    How Google Search handles HTTP status codes, Google
  • Key pages say what they offer in the titlePass

    The title says what the page offers. Google asks for descriptive titles. SearchPilot's test of putting the location at the start of a healthcare provider's titles predicted 8.5% more organic sessions.

    Adding Location to the Start of Title Tags, SearchPilot
  • Each page has a clear address and place in your sitePass

    All 2 audits in this goal pass. Google uses one canonical address per page, recommends readable words rather than long ID numbers, and can show a breadcrumb trail in desktop results when the page marks one up.

    How to Specify a Canonical with rel="canonical" and Other Methods, Google
  • Pages open without detoursPass

    Avoid multiple page redirects: the page only switches to https or adds or drops www. Chrome says each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

    Avoid multiple page redirects, Chrome
69

Understand

Do they understand who you are and what you offer?

25% of your grade · 5 of 7 goals pass

  • Your business is described in structured dataFail

    The structured data lacks the business type, apartment complex, apartment on /search, and service on /related-life. The page does not state the business's address, keywords, latitude, longitude, opening hours, price range, and telephone. Structured data spares an assistant from guessing what a page means. Google says it gives explicit clues about a page; Bing says it may support clearer grounding and promises nothing.

    • The structured data names no type: https://www.relatedrentals.com/
    • Not in the page's structured data: https://www.relatedrentals.com/
    • Not in the page's structured data: https://www.relatedrentals.com/search

    What to do Ask whoever runs your site to mark the business up with the most specific schema.org type that fits it, to add the facts this goal lists to the structured data of the pages that show them, and to state on the page any detail this goal says the page does not state.

    For your web team: Add a JSON-LD script whose "@type" is the most specific schema.org type that fits the business, with each missing property set to the value the page shows, a node for each missing type on the page that shows it, and the value of each detail the page does not state in the text of the page. schema.org lists every type, its subtypes and the properties of each.

    About Usage Statistics, schema.org
  • Headings give each page an outlineFail

    Heading elements are not in a sequentially-descending order Google's guide to AI features says headings give a page a clear structure.

    • Fix any of the following: Heading order invalid: <h5 class="image-card__title">: https://relatedrentals.com/

    What to do Ask the people who run your site to give each page one main heading and to put the headings under it in order.

    For your web team: Use h1 once, then h2 to h6 without skipping a level, and remove or fill any heading element that has no text.

    Optimizing your website for generative AI features on Google Search, Google
  • Your key facts are in the page itselfPass

    Scripts add 33 pieces of text your server does not send, and none of it is what visitors come to the page for. Claude's web fetch tool does not support pages that fill in their text with JavaScript, and Google reads such a page only after its first HTML, once it reaches the rendering queue. A page whose first response is empty waits or looks empty.

    Understand JavaScript SEO basics, Google Search Central
  • Every page has its own summary for search resultsPass

    The description is the page's own and reads as a summary. Google can show a page's meta description as its snippet and asks for a different one on every page. It is less likely to show a list of keywords, so a specific summary has the best chance of being used.

    How to Write Meta Descriptions, Google
  • Images describe themselvesPass

    All 2 audits in this goal pass. Alt text is a short written description of an image. Google calls it the most important attribute for adding metadata about an image, and it also uses computer vision on the picture. It asks for descriptive file names.

    Image SEO Best Practices, Google
  • Pages say which language they are inPass

    All 2 audits in this goal pass. WCAG requires the language of each page to be set in its code, so software reads it with the right rules and voice.

    Rule html-has-lang: <html> element must have a lang attribute, Deque axe
  • Lists and tables are built as lists and tablesPass

    All 2 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires the structure a page shows on screen to be in its markup as well, and the axe rules check lists and tables for it.

    Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe
76

Act

Can they use your site for a shopper?

25% of your grade · 4 of 8 goals pass

  • Your site offers tools to AI assistantsMust haveFail

    Your home page offers no tools to AI assistants. WebMCP lets an assistant book or reserve through a site's own code instead of guessing its way around the screen.

    A must have. While it fails, your letter stays at B or lower.

    • PageSpeed's "WebMCP tools registered" audit lists no tool: https://relatedrentals.com/

    What to do Ask whoever runs your site to expose the main action on your site, such as booking or contacting you, as a WebMCP tool.

    For your web team: Call document.modelContext.registerTool({ name, description, inputSchema, execute }) as the home page loads, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or .

    WebMCP for developers, Chrome
  • Text is readablePartial

    1 of the 3 audits in this goal falls short: Background and foreground colors do not have a sufficient contrast ratio. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

    • Fix any of the following: Element has insufficient color contrast of 3.75 (foreground color: #8e8273, background color: #ffffff, font size: 7.5pt (10px), font weight: normal). Expected contrast ratio of 4.5:1: <span class="filter-bar__label">: https://relatedrentals.com/

    What to do Ask the people who run your site to darken pale text and to underline the links inside paragraphs.

    For your web team: Reach a contrast ratio of 4.5 to 1 for normal text, mark links in text with more than color, and leave user-scalable and maximum-scale out of the viewport tag.

    Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe
  • Buttons and links are big enough to tapPartial

    1 of the 2 audits in this goal falls short: Touch targets do not have sufficient size or spacing. web.dev recommends tap targets of around 48 pixels, and WCAG sets a minimum of 24 by 24 pixels.

    • Fix any of the following: Target has insufficient size (50.6px by 17px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 23.8px instead of at least 24px.: <a href="https://www.relatedrentals.com/blog" target="_blank">: https://relatedrentals.com/

    What to do Ask the people who run your site to make small buttons and tightly packed links bigger on phones.

    For your web team: Make each target at least 24 by 24 CSS pixels, or leave enough space around smaller ones, and aim for around 48 pixels. Set width=device-width in the viewport tag so taps answer at once.

    Accessible tap targets, Google
  • Custom controls announce what they arePass

    Elements with role="dialog" or role="alertdialog" have accessible names. WCAG, the web accessibility standard most laws point to, requires every control to expose its name and role to assistive technology and software.

    Accessibility for agents, Chrome
  • Extra labels on controls are used correctlyPass

    All 11 audits in this goal pass. Wrong ARIA tells an assistant a control is something it is not. WAI-ARIA defines the roles and attributes that are valid, and the axe rules check them.

    Rule aria-roles: ARIA roles used must conform to valid values, Deque axe
  • Visitors can move around the pagePass

    All 3 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires every function of a page to work from a keyboard.

    Accessibility for agents, Chrome
  • Assistants can read your page's controlsPass

    Accessibility tree is well-formed (All audits passed) Chrome says agents review the accessibility tree to find what they can click or fill in, and missing labels can block them.

    Accessibility for agents, Chrome
77

Performance

Is it fast and sound for the person who clicks through?

Speed comes from real visitors of your page over the last 28 days when Google has their numbers, and from a test on a phone when it does not.

25% of your grade · 4 of 10 goals pass

  • Repeat visitors get a faster pageFail

    Use efficient cache lifetimes (Est savings of 1,571 KiB) web.dev says fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 1,571 KiB): https://www.relatedrentals.com/sites/default/files/styles/hero_teaser_small_2x/public/2024-02/The-Square_Daytime-Property-Shot_Large.jpg.webp?h=4997dc06&itok=w6YoKrHd
    • Use efficient cache lifetimes (Est savings of 1,571 KiB): https://www.relatedrentals.com/sites/default/files/styles/hero_teaser_small_2x/public/2019-05/Boston.jpg.webp?h=aaae50ed&itok=32DjP0Ue
    • Use efficient cache lifetimes (Est savings of 1,571 KiB): https://www.relatedrentals.com/sites/default/files/styles/hero_teaser_small_2x/public/2019-05/washington.jpg.webp?h=aaae50ed&itok=ORd-ii0t

    What to do Ask the people who run your site to let browsers keep images, scripts and styles between visits.

    For your web team: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag.

    Prevent unnecessary network requests with the HTTP Cache, Google
  • The main content shows up quicklyPartial

    2 of the 3 audits in this goal fall short: Largest Contentful Paint is 2.5 s for real visitors of this page, last 28 days, which Google rates needs improvement and Speed Index (13.0 s). Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. LCP is how long the main picture or text takes to appear, and visitors leave slow pages. web.dev says 2.5 seconds or less is good, one of Google's three Core Web Vitals.

    • Largest Contentful Paint is 2.5 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://relatedrentals.com/
    • Speed Index (13.0 s): https://relatedrentals.com/
    • Render-blocking requests (Est savings of 3,320 ms): https://www.relatedrentals.com/sites/default/files/css/css_Pt55UGPFt8uFpERPePGwq5uZ7QPcXyzKRGvDJvG8q5o.css?delta=1&language=en&theme=related&include=eJyFUtFuwyAM_KGQfFJkkmvCZDCzYW329aNZ00xVpT1xHGffYaAPuo0sNEMHOnFfVhXvoR2lEryU4bH2F9HYefqWYWHxxK6siCEtnUcp0BG3LIZ5vARuWxsWJChxNzGZbYMnw4EjzGiBHfskczsTRUMaicM3ukxKi1JebZi1ZuL-ZPqacvUcbMXcKZgK5uGez7maQnGKzworrkhVt-c-RC_RD_rZ2rlLZXbXMJfVTaRSDewmSQWpvJOf8CFqVcxS_xHvLitUmlVzMpBO67uSr4CrQ_R_LrpTbpWI3IboplACrPVO4BfNPgwT1heDMatkaNmGB-EOwkXxgdGi3T_Dqd9ym6eC4lnxpDrbrCD-vvDd2HZ766PMlfEDqKPuHg

    What to do Ask the people who run your site to make the first screen load faster on phones, starting with its biggest image.

    For your web team: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back.

    Web Vitals, Google
  • Images are the right sizePartial

    1 of the 4 audits in this goal falls short: Improve image delivery (Est savings of 943 KiB). Chrome says serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 943 KiB): <img loading="lazy" width="529" height="355" src="https://www.relatedrentals.com/sites/default/files/styles/hero_teaser_smal…" alt="">: https://www.relatedrentals.com/sites/default/files/styles/hero_teaser_small_2x/public/2024-02/The-Square_Daytime-Property-Shot_Large.jpg.webp?h=4997dc06&itok=w6YoKrHd

    What to do Ask the people who run your site to resize and compress your images before they go on the page.

    For your web team: Serve several sizes with srcset and sizes, use a modern format such as WebP or AVIF, and keep each image's width and height in the proportion it is shown.

    Properly size images, Chrome
  • The page does not weigh muchPartial

    4 of the 8 audits in this goal fall short: Avoid enormous network payloads (Total size was 28,742 KiB), Reduce unused JavaScript (Est savings of 832 KiB), Reduce unused CSS (Est savings of 74 KiB), and Legacy JavaScript (Est savings of 19 KiB). Chrome says large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    • Avoid enormous network payloads (Total size was 28,742 KiB), from Vimeo: https://vod-adaptive-ak.vimeocdn.com/exp=1792619989~acl=%2Fa75955c7-406a-49f6-90d5-e491c028afe2%2Fpsid%3Dece26eba2f4778103a5e69fba87f6612a0d0fc221792616389%2F%2A~hmac=89a7f0be4c9189c81e6769606a76557733a0580453a5890d33b6d8de7c130e84/a75955c7-406a-49f6-90d5-e491c028afe2/psid=ece26eba2f4778103a5e69fba87f6612a0d0fc221792616389/v2/range/prot/cmFuZ2U9NDM2NDEyNy04ODE4Mjkz/avf/134a772e-98fb-4def-80a4-441cec425124.mp4?pathsig=8c953e4f~BG9NvVb2HLDlMYNtYDMP14A7atPdo6Gq4fmHTS-XSAE&r=dXMtY2VudHJhbDE%3D&range=4364127-8818293
    • Reduce unused JavaScript (Est savings of 832 KiB), from Vimeo: https://f.vimeocdn.com/p/4.46.132/js/player.module.js
    • Reduce unused CSS (Est savings of 74 KiB): https://www.relatedrentals.com/sites/default/files/css/css_Pt55UGPFt8uFpERPePGwq5uZ7QPcXyzKRGvDJvG8q5o.css?delta=1&language=en&theme=related&include=eJyFUtFuwyAM_KGQfFJkkmvCZDCzYW329aNZ00xVpT1xHGffYaAPuo0sNEMHOnFfVhXvoR2lEryU4bH2F9HYefqWYWHxxK6siCEtnUcp0BG3LIZ5vARuWxsWJChxNzGZbYMnw4EjzGiBHfskczsTRUMaicM3ukxKi1JebZi1ZuL-ZPqacvUcbMXcKZgK5uGez7maQnGKzworrkhVt-c-RC_RD_rZ2rlLZXbXMJfVTaRSDewmSQWpvJOf8CFqVcxS_xHvLitUmlVzMpBO67uSr4CrQ_R_LrpTbpWI3IboplACrPVO4BfNPgwT1heDMatkaNmGB-EOwkXxgdGi3T_Dqd9ym6eC4lnxpDrbrCD-vvDd2HZ766PMlfEDqKPuHg

    What to do Ask the people who run your site to remove code and files the page does not use.

    For your web team: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size.

    Avoid enormous network payloads, Chrome
  • The page loads without errorsPartial

    3 of the 7 audits in this goal fall short: Issues were logged in the Issues panel in Chrome Devtools, Uses deprecated APIs (1 warning found), and Uses third-party cookies (2 cookies found). Chrome says an error in the console means a problem on your page that you need to resolve.

    • Issues were logged in the Issues panel in Chrome Devtools: https://relatedrentals.com/
    • Uses deprecated APIs (1 warning found): https://relatedrentals.com/
    • Uses third-party cookies (2 cookies found), from Vimeo: https://player.vimeo.com/video/1179609030?background=1

    What to do Ask the people who run your site to open the page in a browser's developer tools and clear the errors it lists.

    For your web team: Fix each console error and browser issue, replace deprecated APIs, publish source maps for your scripts, and start the document with a doctype and a charset.

    Browser errors were logged to the console, Chrome
  • Served fast from servers near your visitorsPartial

    1 of the 5 audits in this goal falls short: Document request latency (Est savings of 111 KiB). A CDN keeps copies of your site on servers close to each visitor, so pages arrive sooner. Chrome says a CDN reduces the network latency that slows a server's first response.

    • Document request latency (Est savings of 111 KiB): https://relatedrentals.com/
    • Network Round Trip Times (0 ms): https://relatedrentals.com/
    • Server Backend Latencies (30 ms): https://relatedrentals.com/

    What to do Ask the people who run your site to put a CDN in front of it and to turn on compression and caching.

    For your web team: Serve the page through a CDN or edge network over HTTP/2 or HTTP/3, compress text with gzip or Brotli, cache the document at the edge, avoid redirects, and send Strict-Transport-Security with a max-age above zero.

    Reduce server response times (TTFB), Chrome
  • The page responds as soon as it appearsPass

    Interaction to Next Paint is 170 ms for real visitors of this page, last 28 days, which Google rates good. INP is the wait between a tap and the page responding, and under 200 milliseconds is good. Total Blocking Time, the lab test's stand-in, has the same bar.

    Total Blocking Time (TBT), Google
  • The page does not jump around while it loadsPass

    Cumulative Layout Shift is 0.01 for real visitors of this page, last 28 days, which Google rates good. CLS measures how much the page jumps while it loads, which makes people tap the wrong thing. web.dev names it one of three Core Web Vitals, and 0.1 or less is good.

    Web Vitals, Google
  • Visitors are on a secure connectionPass

    Uses HTTPS web.dev says a secure connection helps prevent intruders tampering with traffic between your site and its visitors.

    Why HTTPS matters, Google
  • Visitors are not interrupted on arrivalPass

    All 3 audits in this goal pass. Users are mistrustful of or confused by pages that ask for their location as soon as they load.

    Requests the geolocation permission on page load, Chrome

Watch an assistant search for this site

This scan graded the site on its own. The journey sends an assistant to search the way a shopper would, then shows where it got through and where it stopped.

3rd of 3 local business sites graded so far. See the board.

Get a site that keeps itself ready

Get this site rebuilt in Clutch. It grades itself as assistants change and fixes what slips, so it stays ready on its own. You approve the new site before it goes live.

How we grade