SEO/GEO report — https://originaluniqueart.com/sl/art/john-singer-sargent-st…

Section A · The work

What to fix first

25 recommendations, 12 critical.

Guide

This section answers: What should I fix on this page, and in what order? Open guide

Words used

Quick win
Critical

25recommendations, each from a check point that did not pass

Help Reading the plan: This is the whole report turned into a to-do list for this page: 25 recommendation(s), each one coming from a check point that did not pass. You do not need to understand SEO to use it — work from the top down, and ignore the rest of the report until you have cleared what is here. Nothing below is theory: every line was measured on this page's own content and data. Read more

Careful Timing: Expect weeks, not days. Fixing a tag or adding structured data is seen by Google within days; rewriting or deepening content usually takes 4 to 12 weeks to change your position, and earning links or AI citations is slower still. That is normal, and it is why the plan separates work you finish today from work that pays off later. Read more

How to use this plan

Start with the blue "quick wins" list. Those are minutes of work each, in your page editor — no writing, no developer.
Then take the red "critical" list in order. It is sorted worst-first: the first line is the single thing holding this page back the most. Do them one at a time — three real fixes beat twenty half-fixes.
Hand the "developer task" lines to whoever maintains the site, in one batch. Copy the line's "What to do" text into your message: it is written to be actionable as-is.
Mark each line done with the "I did this" button. It stays visible, struck through, so you can see what is waiting for confirmation. Advice that does not apply to this page — "Dismiss" — moves to the bottom and stops cluttering the plan.
When you have applied a batch, use "Re-collect all data" in the Progress card above. The report then measures the live page again, the score history line records the change, and this plan rebuilds itself from the new data.

What kind of work is waiting for you:

quick copy-paste 1 — a few minutes each in your page editor or CMS. No writing and no developer: this is the work you can do yourself, today.
content work 9 — writing or reorganising the text of the page — typically an hour to a day. This is what wins new searches, and what AI assistants actually quote.
developer task 10 — a change in the code, the template or the server settings. Send these to whoever maintains your website; each one is usually a small, well-defined job.
outreach (ongoing) 3 — getting other websites to mention or link to this page. The slowest work, but also the hardest for a competitor to copy — a few actions a month is enough.

Each line below is built the same way: What to do (the fix, in plain words), What we measured on your site (the finding it comes from), Why it matters (what it changes for your visibility) and Where to see the detail (a link back up to the section with the underlying data).

Copies the list as plain text — ready to paste into an email, a ticket or your notes.

QUICK WINS — a few minutes each, no developer needed

- Declared keyword targets (D. Keyword targets: intent vs results)
  What to do: Choose the 3-10 searches this page should be found for (the words a customer would type when your page is the answer), and declare them comma-separated in a <meta name="keywords"> tag in the page's code. Google itself ignores the tag, so there is no risk — but this report will then check each declared target against real Google results: how hard it is, whether the page ranks for it, and which page of your site captures it instead.
  Found: No meta keywords declared on the page

DEVELOPER TASKS from the SEO/GEO report

- [CRITICAL] Largest Contentful Paint (LCP) (F. Performance (Google Lighthouse), scored 25/100)
  What to do: At 5.4 s the main content is in Google's 'poor' zone (over 4 s) — many visitors leave before seeing anything, and Google penalizes it directly. Fixes for your developer, in order: compress the big top image and load it in priority ('preload'), make the server answer faster (caching, CDN), and remove the scripts that block the page from displaying.
  Found: 5.40 s
  Why it matters: How long a visitor waits before the page's main content (usually the big image or headline) appears on a phone. Google's rule of thumb: under 2.5 seconds is good, over 4 seconds is poor — and visitors give up quickly on pages that show nothing.

- [CRITICAL] Cumulative Layout Shift (CLS) (F. Performance (Google Lighthouse), scored 25/100)
  What to do: At 0.39 the page jumps around badly while loading (Google's 'poor' zone starts at 0.25) — visitors misclick and Google penalizes it. Fixes for your developer: declare width and height on every image and embed so the browser reserves their space in advance, never insert banners above existing content after load, and preload the custom fonts so text doesn't reflow.
  Found: 0.392
  Why it matters: How much the page visibly jumps around while it loads — text moving as images pop in, buttons shifting under the visitor's finger. Google's rule: under 0.1 is good, over 0.25 is poor.

- [CRITICAL] Image dimensions (CLS) (D. Images, scored 31/100)
  What to do: 40 of 127 images already declare their size — the remaining 87 still make the layout jump while they load. Ask your developer to add width and height attributes to those image tags too (or update the site's image component to do it everywhere automatically), so the page stops jumping entirely.
  Found: 40/127 images declare width and height
  Why it matters: Whether each image declares its width and height in the code. When it does, the browser reserves the right space before the image arrives; when it does not, the page visibly jumps around while loading — an annoyance Google measures (as 'CLS') and penalizes.

- [TO IMPROVE] Performance score (F. Performance (Google Lighthouse), scored 54/100)
  What to do: At 54/100 the page is workable but slower than it should be on mobile. The usual levers: compress the images and serve them in modern formats, make below-screen images load only on scroll, remove or delay non-essential scripts (old analytics, widgets), and enable caching or a CDN so repeat visits are instant. The detailed measurements below show which of these weighs most — share them with your developer.
  Found: score 54 / 100
  Why it matters: Google Lighthouse's overall speed score of the live page on a phone (0-100). Speed matters twice: Google uses it in its ranking, and slow pages lose visitors before anything shows — every extra second of loading costs sales.

- [TO IMPROVE] Script weight (F. Technical & AI readiness (GEO), scored 65/100)
  What to do: The page loads 21 JavaScript files — more than the ~10 of a lean page. Review them with your developer: remove tools you no longer use (old analytics, abandoned widgets), combine what remains, and load non-essential ones (chat, social buttons) only after the page has displayed.
  Found: 21 external script(s) from 0 domain(s)
  Why it matters: How many JavaScript files the page loads, and from how many different providers (analytics, chat widgets, ads...). Every script adds download and processing time; pages accumulate them over the years and rarely clean up.

- [TO IMPROVE] Text-to-HTML ratio (D. Content structure & quality, scored 70/100)
  What to do: Only 7.7% of this page's code is actual readable text — workable, but below the ~10% of a lean page. Two ways to improve it, both good for SEO: add more real text content to the page (the easy win), and/or ask your developer to slim the page down (remove unused scripts and styling). A lighter page also loads faster, which Google rewards.
  Found: 7.7% (28386 text bytes / 369754 HTML bytes)
  Why it matters: How much of the page's code is actual readable text versus technical code (layout, scripts, styling). A very low share means the page carries a lot of technical weight for little content — which slows it down and makes it harder to crawl.

- [TO IMPROVE] Broken link patterns (E. Links, scored 70/100)
  What to do: 18 of the page's 231 links lead nowhere (their destination is empty or '#'). If they are real links, point them at real page addresses. If they only open a menu or accordion, ask your developer to code them as buttons instead of links — visitors see no difference, but crawlers stop wasting time on dead ends.
  Found: 18 suspicious href(s) out of 231 link(s) (7.8%)
  Why it matters: How many links lead nowhere — their destination is empty, '#' or a JavaScript action instead of a real page address. These are usually menu buttons coded as links; crawlers treat them as dead ends.

- [TO IMPROVE] Accessibility score (F. Performance (Google Lighthouse), scored 79/100)
  What to do: Fix the usual top offenders first: text whose color blends into the background (raise the contrast), images without descriptions, and form fields or icon buttons without a visible label. Each fix helps disabled visitors, and the same information helps search engines and AI assistants understand the page.
  Found: score 79 / 100
  Why it matters: How usable the page is for people with disabilities: enough color contrast to read, descriptions on images, labeled buttons and forms, keyboard navigation. Accessible pages are also easier for search and AI engines to understand — the same labels help both.

- [OPPORTUNITY] Real-user Core Web Vitals (F. Performance (Google Lighthouse))
  What to do: Nothing to fix here: Google only publishes real-user speed for pages with enough traffic to stay anonymous, so this is a statement about audience size, not about speed. The Lighthouse lab numbers above are the measurement to work from until the page gets more visitors.
  Data: No real-user data — Google has too few visits to report

- [OPPORTUNITY] Top speed opportunities (F. Performance (Google Lighthouse))
  What to do: Hand this list to your developer as-is, top item first — it is Lighthouse's own measurement of which fix buys the most seconds on THIS page, so there is no need to guess where to start.
  Data: Render-blocking requests (saves ≈2.5 s); Use efficient cache lifetimes (saves ≈1.3 s); Improve image delivery (saves ≈1.0 s); Reduce unused CSS (saves ≈0.5 s); Font display (saves ≈0.1 s); Reduce unused JavaScript — Est savings of 106 KiB; Avoid large layout shifts — 1 layout shift found

Do these today — quick wins (1)

Help Quick wins: The lines from all three groups below that need only a few minutes each and no special skill. They are listed here as a shortcut — the full explanation of each one is in its own group underneath. If you only have one hour for this page this week, spend it here. Read more

Declared keyword targets — M. Keyword targets: intent vs results

1. Fix first — critical (12)

Help Critical: These check points scored under 50 out of 100, which means they are actively holding this page back right now — not "could be better", but "is costing you visitors today". Google and the AI assistants can only work with what they find on the page, and on these points they find something broken, missing or contradictory. Fix them in this order: the list starts with the worst score, which is where the effort pays off most. Read more

Backlink volume outreach (ongoing) (E. Backlink profile — this check scores 20/100)
What to do: No other website links to this page yet, so it has no outside votes of confidence. Start earning some: publish content other sites want to reference (guides, original photos or data), list your business in the serious directories of your industry, and personally propose the page to blogs and partners in your niche. Even a handful of real links makes a difference for a page starting from zero.

What we measured on your site: 0 backlinks found

Why it matters: How many other websites link to this page. Each such link ('backlink') works like a vote of confidence — they remain the strongest factor for ranking on Google besides the content itself.

Where to see the detail: the E. Backlink profile section shows this check with the data it is based on.
Indexed backlink totals outreach (ongoing) (E. Authority & search traffic — this check scores 20/100)
What to do: The whole web index counts ZERO links to this page — no outside site has ever voted for it. Start from the accessible end: serious industry directories, partners and suppliers, then propose the page to blogs in your niche. For a page at zero, even 2-3 real linking sites make a measurable difference.

What we measured on your site: 0 backlink(s) from 0 referring domain(s) (0 main domain(s))

Why it matters: The total count of links pointing to this page across the whole web index, and how many DIFFERENT websites they come from. The number of different linking websites is what matters most — each one is a separate vote of confidence.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Estimated organic traffic content work (E. Authority & search traffic — this check scores 20/100)
What to do: Google currently sends this page essentially no visitors — it either ranks for nothing, or only beyond position 10 where nobody clicks. The fix starts with content and targeting, not fine-tuning: make the page genuinely answer specific searches (see the keyword sections), then build its authority with links.

What we measured on your site: ≈ 0 visit(s) / month from Google organic

Why it matters: An estimate of how many visitors this page receives from Google every month, without any advertising. It is computed from every search the page appears for: how many people make that search, times the share of clicks its position typically gets.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Keyword footprint content work (E. Authority & search traffic — this check scores 20/100)
What to do: The page appears for NO search at all in Google's top 100 — it is effectively invisible. Before optimizing details, fix the foundation: enough specific text content on a clearly defined topic (see the content section), then authority through links. A page needs both to enter the top 100 for anything.

What we measured on your site: 0 keyword(s) in the Google top 100

Why it matters: For how many different Google searches this page appears somewhere in the first 100 results. A wide footprint means the page matches many searches — and every improvement to the page lifts all of them at once.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Largest Contentful Paint (LCP) developer task (F. Performance (Google Lighthouse) — this check scores 25/100)
What to do: At 5.4 s the main content is in Google's 'poor' zone (over 4 s) — many visitors leave before seeing anything, and Google penalizes it directly. Fixes for your developer, in order: compress the big top image and load it in priority ('preload'), make the server answer faster (caching, CDN), and remove the scripts that block the page from displaying.

What we measured on your site: 5.40 s

Why it matters: How long a visitor waits before the page's main content (usually the big image or headline) appears on a phone. Google's rule of thumb: under 2.5 seconds is good, over 4 seconds is poor — and visitors give up quickly on pages that show nothing.

Where to see the detail: the F. Performance (Google Lighthouse) section shows this check with the data it is based on.
Cumulative Layout Shift (CLS) developer task (F. Performance (Google Lighthouse) — this check scores 25/100)
What to do: At 0.39 the page jumps around badly while loading (Google's 'poor' zone starts at 0.25) — visitors misclick and Google penalizes it. Fixes for your developer: declare width and height on every image and embed so the browser reserves their space in advance, never insert banners above existing content after load, and preload the custom fonts so text doesn't reflow.

What we measured on your site: 0.392

Why it matters: How much the page visibly jumps around while it loads — text moving as images pop in, buttons shifting under the visitor's finger. Google's rule: under 0.1 is good, over 0.25 is poor.

Where to see the detail: the F. Performance (Google Lighthouse) section shows this check with the data it is based on.
Page authority rank outreach (ongoing) (E. Authority & search traffic — this check scores 25/100)
What to do: The page has NO measurable authority yet (rank 0) — the web's link graph barely knows it exists, so it can only rank on searches nobody competes for. Both levers matter from scratch: earn its first real links from outside websites (see the backlink section), and link to it prominently from your own most powerful pages (usually the home page).

What we measured on your site: rank 0 / 1000

Why it matters: The page's overall 'authority' score from 0 to 1000 — a measure of all the link power it has accumulated from other sites, similar to Google's original PageRank. 50+ means real authority; 400+ is a strong page that can compete on hard keywords.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Measured visits (Analytics) content work (E. Authority & search traffic — this check scores 25/100)
What to do: Nobody reached this page from a search during the measured period. If it ranks for keywords (the section below), the titles and descriptions are not earning the click; if it ranks for nothing, it is a content problem, not a copy one.

What we measured on your site: 0 visit(s) landed here, 0 from organic search (0%)

Why it matters: How many visits actually STARTED on this page, and how many of them came from a Google search. Measured by the site's own Analytics, so unlike the estimates above it is not a model of the page — it is the page.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Measured search performance (Search Console) (E. Authority & search traffic — this check scores 30/100)
What to do: Google shows this page far more often than people click it — the listing is losing the auction for attention at its own position. That is a title-and-description job: the proposed rewrites in the drafts section exist for exactly this page.

What we measured on your site: 1 impression(s), 0 click(s) (0.0% of showings earned the click) at average position 25.0

Why it matters: How often Google actually showed this page in its results, at what average position, and how many of those showings earned the click — counted by Google itself, not modelled from third-party data like the estimates above.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Image dimensions (CLS) developer task (D. Images — this check scores 31/100)
What to do: 40 of 127 images already declare their size — the remaining 87 still make the layout jump while they load. Ask your developer to add width and height attributes to those image tags too (or update the site's image component to do it everywhere automatically), so the page stops jumping entirely.

What we measured on your site: 40/127 images declare width and height

Why it matters: Whether each image declares its width and height in the code. When it does, the browser reserves the right space before the image arrives; when it does not, the page visibly jumps around while loading — an annoyance Google measures (as 'CLS') and penalizes.

Where to see the detail: the D. Images section shows this check with the data it is based on.
Measured engagement (Analytics) content work (E. Authority & search traffic — this check scores 35/100)
What to do: Most visitors leave this page without doing anything. Before buying more traffic for it, check that the first screen answers the search that brought them, that the page loads fast on a phone (the performance section), and that there is somewhere obvious to go next.

What we measured on your site: 0% engaged, 0% left without engaging

Why it matters: The share of visitors who actually engaged with the page instead of leaving straight away. A page can be technically perfect and still lose everyone in the first five seconds; this is the check that can tell.

Where to see the detail: the E. Authority & search traffic section shows this check with the data it is based on.
Author and date signals (E-E-A-T) content work (E. Trust & E-E-A-T — this check scores 45/100)
What to do: The page is completely anonymous and undated — no author, no byline, no date anywhere in the code. Show who is behind this content and how fresh it is: add a visible author line ('By [name], [role]' — with a short bio if possible) and a visible published or updated date near the top of the content. Trust signals like these cost nothing and make the page more credible to visitors, to Google, and to AI assistants choosing which sources to cite.

What we measured on your site: none

Why it matters: Whether the page shows who wrote it and when it was published or updated. Google calls this E-E-A-T (experience, expertise, authority, trust): named authors and visible dates make a page look trustworthy — anonymous, undated pages look less citable to both Google and AI assistants.

Where to see the detail: the E. Trust & E-E-A-T section shows this check with the data it is based on.

2. Then improve (8)

Help To improve: These scored between 50 and 79 out of 100: they work, but they leave rankings, clicks or citations on the table. Nothing here is urgent — come back to this group once the critical list is empty. This is also where a page moves from "correct" to "hard to beat", so it is worth real time once the basics are done. Read more

Performance score developer task (F. Performance (Google Lighthouse) — this check scores 54/100)
What to do: At 54/100 the page is workable but slower than it should be on mobile. The usual levers: compress the images and serve them in modern formats, make below-screen images load only on scroll, remove or delay non-essential scripts (old analytics, widgets), and enable caching or a CDN so repeat visits are instant. The detailed measurements below show which of these weighs most — share them with your developer.

What we measured on your site: score 54 / 100

Why it matters: Google Lighthouse's overall speed score of the live page on a phone (0-100). Speed matters twice: Google uses it in its ranking, and slow pages lose visitors before anything shows — every extra second of loading costs sales.

Where to see the detail: the F. Performance (Google Lighthouse) section shows this check with the data it is based on.
Review & rating integrity content work (E. Trust & E-E-A-T — this check scores 55/100)
What to do: The page declares a star rating (AggregateRating) but marks up no individual review. Show real customer reviews on the page and mark a few of them up with Review schema (author, rating, text), so the declared average is verifiably backed — otherwise Google may ignore or penalize the rating markup.

What we measured on your site: AggregateRating declared, but no Review markup

Why it matters: Whether the ratings the page declares in its structured data are backed by actual reviews. Google requires declared ratings to reflect reviews visible on the page — a star rating with no reviews behind it can be treated as spammy structured data and cost all rich results.

Where to see the detail: the E. Trust & E-E-A-T section shows this check with the data it is based on.
Script weight developer task (F. Technical & AI readiness (GEO) — this check scores 65/100)
What to do: The page loads 21 JavaScript files — more than the ~10 of a lean page. Review them with your developer: remove tools you no longer use (old analytics, abandoned widgets), combine what remains, and load non-essential ones (chat, social buttons) only after the page has displayed.

What we measured on your site: 21 external script(s) from 0 domain(s)

Why it matters: How many JavaScript files the page loads, and from how many different providers (analytics, chat widgets, ads...). Every script adds download and processing time; pages accumulate them over the years and rarely clean up.

Where to see the detail: the F. Technical & AI readiness (GEO) section shows this check with the data it is based on.
Heading hierarchy content work (D. Content structure & quality — this check scores 70/100)
What to do: Some heading levels are skipped (e.g. a section jumps from H2 straight to H4). Headings should nest like a document outline: H1 for the page title, H2 for sections, H3 for sub-sections. Fix the skipped levels in your editor's heading dropdown so the outline reads logically.

What we measured on your site: 125 heading(s), 24 H2, levels skipped

Why it matters: How the page's headings are organized: one main title (H1), then section headings (H2), then sub-sections (H3) — like a document outline, without skipping levels. This outline is how Google and AI assistants cut the page into sections they can understand and quote.

Where to see the detail: the D. Content structure & quality section shows this check with the data it is based on.
Text-to-HTML ratio developer task (D. Content structure & quality — this check scores 70/100)
What to do: Only 7.7% of this page's code is actual readable text — workable, but below the ~10% of a lean page. Two ways to improve it, both good for SEO: add more real text content to the page (the easy win), and/or ask your developer to slim the page down (remove unused scripts and styling). A lighter page also loads faster, which Google rewards.

What we measured on your site: 7.7% (28386 text bytes / 369754 HTML bytes)

Why it matters: How much of the page's code is actual readable text versus technical code (layout, scripts, styling). A very low share means the page carries a lot of technical weight for little content — which slows it down and makes it harder to crawl.

Where to see the detail: the D. Content structure & quality section shows this check with the data it is based on.
Broken link patterns developer task (E. Links — this check scores 70/100)
What to do: 18 of the page's 231 links lead nowhere (their destination is empty or '#'). If they are real links, point them at real page addresses. If they only open a menu or accordion, ask your developer to code them as buttons instead of links — visitors see no difference, but crawlers stop wasting time on dead ends.

What we measured on your site: 18 suspicious href(s) out of 231 link(s) (7.8%)

Why it matters: How many links lead nowhere — their destination is empty, '#' or a JavaScript action instead of a real page address. These are usually menu buttons coded as links; crawlers treat them as dead ends.

Where to see the detail: the E. Links section shows this check with the data it is based on.
Image alt texts content work (D. Images — this check scores 73/100)
What to do: 93 of 127 images already have a description — finish the job on the remaining 34. For each, write a short sentence saying what the image shows, naturally including the words customers search for when it is honest to do so — this is also how your images appear in Google Images. Every site editor has an 'alt text' field on images.

What we measured on your site: 93/127 images have alt text (73%)

Why it matters: How many images carry an 'alt text' — a short written description of what the image shows. It is what blind visitors hear, what Google Images indexes, and how search and AI engines know what your pictures contain.

Where to see the detail: the D. Images section shows this check with the data it is based on.
Accessibility score developer task (F. Performance (Google Lighthouse) — this check scores 79/100)
What to do: Fix the usual top offenders first: text whose color blends into the background (raise the contrast), images without descriptions, and form fields or icon buttons without a visible label. Each fix helps disabled visitors, and the same information helps search engines and AI assistants understand the page.

What we measured on your site: score 79 / 100

Why it matters: How usable the page is for people with disabilities: enough color contrast to read, descriptions on images, labeled buttons and forms, keyboard navigation. Accessible pages are also easier for search and AI engines to understand — the same labels help both.

Where to see the detail: the F. Performance (Google Lighthouse) section shows this check with the data it is based on.

3. Opportunities from the data (5)

Help Opportunities: These are not faults, so they carry no score: they are openings found in this page's own data — searches it nearly wins, keywords it targets without ranking, competitors ahead of it, questions the AI answers with somebody else's site. Repairing the two groups above stops you losing; this group is how you gain. Pick one or two per month and treat them as projects rather than fixes. Read more

AI answers collection (G. AI visibility (questions & answers))
What to do with it: Enable promotion for this page (pages list, Promotion column) to trigger the one-time data collection.

What the data says: Not fetched yet — the task runs once per page when its promotion is enabled and an HTML snapshot is stored

Why it matters: Whether the AI questions/answers of this page (real AI-assistant answers to 5 user questions generated from the page content) were fetched yet.

Where to see the detail: the G. AI visibility (questions & answers) section shows this check with the data it is based on.
Real-user Core Web Vitals developer task (F. Performance (Google Lighthouse))
What to do with it: Nothing to fix here: Google only publishes real-user speed for pages with enough traffic to stay anonymous, so this is a statement about audience size, not about speed. The Lighthouse lab numbers above are the measurement to work from until the page gets more visitors.

What the data says: No real-user data — Google has too few visits to report

Why it matters: What real Chrome visitors measured on this page over the last 28 days, not a simulation. This is the speed data Google uses for ranking.

Where to see the detail: the F. Performance (Google Lighthouse) section shows this check with the data it is based on.
Top speed opportunities developer task (F. Performance (Google Lighthouse))
What to do with it: Hand this list to your developer as-is, top item first — it is Lighthouse's own measurement of which fix buys the most seconds on THIS page, so there is no need to guess where to start.

What the data says: Render-blocking requests (saves ≈2.5 s); Use efficient cache lifetimes (saves ≈1.3 s); Improve image delivery (saves ≈1.0 s); Reduce unused CSS (saves ≈0.5 s); Font display (saves ≈0.1 s); Reduce unu…

Why it matters: The exact fixes Google Lighthouse itself measured as the biggest speed levers on this page, with the loading time each one is estimated to save. This is the concrete to-do list behind the scores above.

Where to see the detail: the F. Performance (Google Lighthouse) section shows this check with the data it is based on.
Competitors on your Google results content work (G. Competitive landscape)
What to do with it: Search Google for your own target keywords and study how myfigurecollection.net presents its pages in the results (titles, descriptions, rich snippets) — it shares the most keywords with you. Start by out-writing the competitors weaker than your site: better titles and content on the shared keywords is enough to pass them, no new links needed.

What the data says: myfigurecollection.net (1 shared keyword(s), avg position 3, rank 524); specfictionshop.com (1 shared keyword(s), avg position 1, rank 354); miraicollectibles.com (1 shared keyword(s), avg position 2…

Why it matters: The domains that rank in Google for the same keywords as this site, ranked by how many keywords you share. Unlike the link-space competitors above, these are found on the result pages themselves — they take the clicks you want even when they share none of your link sources.

Where to see the detail: the G. Competitive landscape section shows this check with the data it is based on.
Declared keyword targets quick copy-paste (D. Keyword targets: intent vs results)
What to do with it: Choose the 3-10 searches this page should be found for (the words a customer would type when your page is the answer), and declare them comma-separated in a <meta name="keywords"> tag in the page's code. Google itself ignores the tag, so there is no risk — but this report will then check each declared target against real Google results: how hard it is, whether the page ranks for it, and which page of your site captures it instead.

What the data says: No meta keywords declared on the page

Why it matters: The keywords the page declares as its targets in its <meta name="keywords"> tag. Google ignores this tag as a ranking signal, so it cannot hurt — but writing your targets there lets this report check each one against reality with a real Google search: does the page actually rank for what it aims at?

Where to see the detail: the D. Keyword targets: intent vs results section shows this check with the data it is based on.

Section B · Standing

How your page scores

Critical

77% overall, 12 critical points.

Guide

This section answers: How good is this page overall, and are my fixes moving the score? Open guide

Words used

Check point
Critical

77%Overall quality: Acceptable

32good

8to improve

12critical

Help The condition scale: Every result in this report — a section, a check point — wears one of four words, from the most urgent:

Critical: Now. It is costing money or visibility today.
Fix soon: This week, before anything new.
Good: Fine as it is; keep going.
Worth knowing: Nothing to fix; good to know.

A grey Info badge is a point with no score: context or a data-driven opportunity rather than a pass/fail check. The overall score is the average of every scored check point (average of the 52 scored check points; the 62 points include informational ones, which carry no score). Read more

Help SEO and GEO: Analysis of this page from its stored HTML snapshot and AkOOre's own measurements. SEO covers how well the page can rank in Google; GEO (Generative Engine Optimization) covers how usable it is as a source for AI answers (ChatGPT, Perplexity, Google AI Overviews). Each check point shows what is checked and why it matters, what was actually found on the page, a quality estimation, and how to fix it when it is not good enough. Read more

This page scores 77% overall — acceptable: 32 of the 52 scored check points pass, 8 need improvement and 12 are critical. On-page, the strongest area is D. Structured data (SEO & GEO) (100%) and the weakest is J. Images (76%). GEO / AI readiness is at 100% — how usable the page is for AI answer engines (server-rendered text, question headings, extractable lists/tables, facts and sources). This number averages every check point tagged (GEO) across all sections, so it can differ slightly from the Technical & AI readiness section score. No backlinks are stored yet, so off-page authority is the main unknown — or the main growth lever. Fastest gains first: Backlink volume (20%), Indexed backlink totals (20%), Estimated organic traffic (20%) — the action plan below is ordered accordingly.

https://originaluniqueart.com/sl/art/john-singer-sargent-studije-mrtve-ptice-8ye3gu-sl/PrintReproduction/ · Snapshot taken Oct. 23, 2026, 6:16 a.m. · Language sl · All 13 sections have data

The report now records its scores each time they change (at most once per day), so from your next fixes on, a score history will appear here showing whether they work.

Applied some fixes on your page? Mark them done in the action plan below, then re-measure the live page with Refresh at the top (every data collection, the paid ones included). Speed fixes have their own button, because checking them is free:

Section C · GEO

Ready for AI answers

Fix soon

Answer-readiness 70 / 100.

Guide

This section answers: Could an AI assistant quote this page as its answer? Open guide

Words used

Being quoted by AI: — appearing in the answers of ChatGPT, Gemini or Google's AI summary.
AI Overviews

70/100AI answer-readiness

Help Reading the score: How usable this page is as a source when ChatGPT, Claude, Perplexity or Google AI Overviews answer a question. Five criteria scored 0–100, then averaged — so the weakest row below is the one to fix first. Read more

Answers a question head-on	85/100 Good	The page identifies the product as a Giclée print of 'Študije mrtve ptice' by John Singer Sargent early on.
States checkable specifics	95/100 Good	Includes specific SKU-like codes with prices (e.g., P118B €10), a total price of €72, and a 100-day return policy.
Ties the facts to the brand	60/100 Fix soon	The subject (Sargent's work) is named, but the brand 'OriginalUniqueArt.com' is not explicitly linked to the facts in th
Structured to be quoted	70/100 Good	The page uses clear headings for 'Artistic Style and Technique' and 'Historical Context'.
Shows who says it and when	40/100 Fix soon	Mentions a 100-day return policy and free worldwide shipping, but lacks a specific author or date.

Nothing quotable no passage on this page could be lifted into an AI answer as it stands — that is what the recommendations below are for.

What to change, highest value first

Include the brand name 'OriginalUniqueArt.com' within the product description or header to strengthen brand attribution.
Add a specific contact method or customer service link near the guarantee section to improve trust signals.

Section D

What Google reads on the page

Fix soon

Guide

This section answers: Does the page tell Google clearly what it is about? Open guide

The title and description, the text and its headings, the structured data, the images, then the searches the page targets.

Head & meta tags

Good

Every scored point passes — 100%.

Guide

This section answers: Do the invisible tags in the page's head tell Google what the page is? Open guide

Words used

Meta description
Main version: — the address you tell Google is the real one when several pages look alike.
Open Graph

data collected 23 Oct 2026

100%9/9 scored points pass.

Help What this section checks: The invisible tags in the page's <head> are what Google reads first and what it shows in its results: the title and description become your 'ad' on the results page, the canonical URL avoids duplicate-content dilution, and social tags control how the page looks when shared. Weak tags here mean fewer clicks even when the page ranks. Read more

Check points of the A. Head & meta tags section
Check point	Found	Quality	How to fix / recommendation
Title tag quick copy-paste The page's title tag — the blue clickable headline shown in Google results (30-65 characters usually shows in full). It is also the single strongest signal telling Google what the page is about, so its words should match what people search for.	"Študije mrtve ptice by John Singer Sargent – Fine Art Print" (59 chars)	Good 100%	—
Meta description quick copy-paste The meta description — the 1-2 grey lines Google shows under the page's headline in its results (about 70-160 characters usually shows in full; there is no fixed limit). It does not change the ranking itself, but it is what convinces searchers to click your result rather than the next one.	"Študije mrtve ptice (1874) by John Singer Sargent as a fine-art giclée print on canvas or paper. Your size, optional frame, shipped worldwide." (142 chars)	Good 100%	—
Canonical URL developer task The 'canonical' tag — a line in the page's code stating the official address of this page. It prevents Google from splitting the page's ranking strength across duplicate addresses (with/without www, tracking parameters, etc.).	https://originaluniqueart.com/sl/art/john-singer-sargent-studije-mrtve-ptice-8ye3gu-sl/	Good 100%	—
Robots directives developer task Special instructions to search engines in the page's code. 'noindex' hides the page from Google entirely, 'nofollow' makes its links count for nothing, and 'max-snippet:0' forbids Google and AI assistants from quoting the page. Having none of these (the default) is what you normally want.	index,follow	Good 100%	—
Language declaration developer task Whether the page's code declares what language its content is written in. Google and AI assistants use this to show the page to people searching in that language.	lang="sl"	Good 100%	—
Mobile viewport developer task Whether the page tells browsers how to display it on a phone screen (the 'viewport' setting). Without it the page appears zoomed-out and unreadable on mobile — and Google judges every site by its MOBILE version first.	width=device-width, initial-scale=1.0	Good 100%	—
Character encoding developer task Whether the page declares its text encoding (how letters and accents are stored). Without it, accented characters and symbols can display as garbage like 'Ã©' for both visitors and search engines.	UTF-8	Good 100%	—
Open Graph tags quick copy-paste The 'Open Graph' tags (og:title, og:description, og:image) — they define the title, text and picture shown when someone shares this page on social networks or in chat apps (WhatsApp, Facebook, LinkedIn, Slack...). Several AI engines also use them as the page's preview card.	og:title, og:description, og:image	Good 100%	—
Hreflang alternates developer task The 'hreflang' tags — lines of code listing the other language versions of this page (English, French...). They let Google send each visitor to the right language version. Only relevant if the site exists in several languages; having none is fine for a single-language site.	33 hreflang link(s) found: ar, bg, cs, da, de, el, en, es, et, fi, fr, hi, hr, hu, it, ja, ka, ko, lt, nl (+13 more)	Worth knowing	—
Favicon developer task The favicon — the small square logo shown in the browser tab and next to your site's name in Google's mobile results. A missing one makes the site look unfinished in the results list.	/static/images/originaluniqueart/favicon-oua.97ff269d9f4a.png	Good 100%	—

Content structure & quality

Good

2 points to improve — 91%.

Guide

This section answers: Is the text deep and well structured enough to rank and be quoted? Open guide

Words used

H1
Heading hierarchy

data collected 23 Oct 2026

91%5/7 scored points pass. Weakest point: Heading hierarchy (70%).

Help What this section checks: Google and AI engines evaluate whether the page genuinely answers the visitor: enough text, one clear H1, a logical heading hierarchy, readable paragraphs, lists and tables. Thin or poorly structured content is the most common reason a page cannot rank no matter its authority. Read more

The heading structure, in page order

H1 Študije mrtve ptice

H2 Opis zbirateljskega predmeta

H2 Biografija umetnika

H2 Giclée tisk / Umetniški tisk

H2 Tehnika in material reprodukcije

H2 Izbira okvirjev za reprodukcijo

H6 White €1 jumped H2 → H6

H6 Blurside €1

H6 Extended €1

H6 P118B €10

H6 P118H €10

H6 P118W €10

H6 P438Z €10

H6 P508JH €12

H6 P508YH €12

H6 P805H €10

H6 P805Z €10

H6 P919BZ €10

H6 P919G €10

H6 P919XJ €10

H6 P959ZH €10

H6 P968JZ €12

H6 W106C €8

H6 W218G €10

H6 W218JH €8

H6 W218Y €10

H6 W307PJ €10

H6 W316G €10

H6 W316PJ €8

H6 W316Y €10

H6 W398PJ €8

H6 W4111J €10

H6 W500HY €15

H6 W500JH €15

H6 W692G €12

H6 W849H €8

H6 W940BG €15

H6 W953PJ €8

H6 H24-GOLD €30

H6 H24-SILVER €30

6 levels are skipped — gaps in the outline, marked above where they happen. First 40 of 125 headings.

Check points of the B. Content structure & quality section
Check point	Found	Quality	How to fix / recommendation
H1 heading content work The main heading (H1) — the big title at the top of the page. There should be exactly one, clearly stating what the page is about: it is the first thing Google and AI assistants read to understand the topic.	One H1: "Študije mrtve ptice"	Good 100%	—
Heading hierarchy content work How the page's headings are organized: one main title (H1), then section headings (H2), then sub-sections (H3) — like a document outline, without skipping levels. This outline is how Google and AI assistants cut the page into sections they can understand and quote.	125 heading(s), 24 H2, levels skipped	Fix soon 70%	How to fix: Some heading levels are skipped (e.g. a section jumps from H2 straight to H4). Headings should nest like a document outline: H1 for the page title, H2 for sections, H3 for sub-sections. Fix the skipped levels in your editor's heading dropdown so the outline reads logically.
Question-form headings (GEO) content work Whether some section headings are written as questions ('How does...?', 'What is...?'). A question heading followed by a direct answer is the content Google's 'People also ask' boxes and AI assistants quote most readily.	3 question heading(s), e.g. "Za kakšno umetniško delo velja "Študije mrtve ptice"?"	Good 100%	—
Content length content work How many words of readable text the page contains. Pages with very little text rarely rank on Google — there is not enough for it to understand — and give AI assistants nothing worth quoting. 600+ useful words is a solid baseline for a page you want to promote.	~4201 words of visible text	Good 100%	—
Text-to-HTML ratio developer task How much of the page's code is actual readable text versus technical code (layout, scripts, styling). A very low share means the page carries a lot of technical weight for little content — which slows it down and makes it harder to crawl.	7.7% (28386 text bytes / 369754 HTML bytes)	Fix soon 70%	How to fix: Only 7.7% of this page's code is actual readable text — workable, but below the ~10% of a lean page. Two ways to improve it, both good for SEO: add more real text content to the page (the easy win), and/or ask your developer to slim the page down (remove unused scripts and styling). A lighter page also loads faster, which Google rewards.
Lists and tables (GEO) content work Whether the page uses bulleted lists, numbered steps or comparison tables. These self-contained blocks are what AI assistants and Google's answer boxes copy word-for-word as ready-made answers.	23 list(s), 0 table(s)	Good 100%	—
Semantic HTML5 structure developer task Whether the page's code labels its zones: <main> for the main content, <nav> for menus, <footer> for the footer... These labels let Google and AI assistants separate your real content from the menus and boilerplate around it.	main, nav, header, footer	Good 100%	—

Structured data (SEO & GEO)

Good

Every scored point passes — 100%.

Guide

This section answers: Does the page describe itself in the structured data search and AI engines read? Open guide

Words used

Schema.org
JSON-LD

data collected 23 Oct 2026

100%4/4 scored points pass.

Help What this section checks: Structured data (JSON-LD 'schema') describes the page to machines in an unambiguous format: what it is, who wrote it, what it offers. Search engines use it for rich results (stars, prices, breadcrumbs) and AI answer engines use it to understand and cite the page — one of the few levers that helps both at once. Read more

See the technical detail

Check points of the D. Structured data (SEO & GEO) section
Check point	Found	Quality	How to fix / recommendation
JSON-LD structured data quick copy-paste Whether the page contains 'structured data' — a hidden block of code that describes the page to machines in a standard format (what it is, who publishes it, what it sells). Google uses it to show rich results (stars, prices, breadcrumbs) and AI assistants use it to understand and trust the page.	Types found: AggregateRating, Answer, Brand, BreadcrumbList, DefinedRegion, EntryPoint, FAQPage, ImageObject, ItemPage, LearningResource, ListItem, MerchantReturnPolicy, MonetaryAmount, Museum, Offer, OfferShippin	Good 100%	—
Main entity schema quick copy-paste Whether the structured data says what the page IS: an Article, a Product, a LocalBusiness... This is what qualifies the page for Google's rich results (stars, price, stock) and helps AI assistants classify and cite it correctly.	Product	Good 100%	—
Organization / entity markup quick copy-paste Whether the structured data identifies WHO is behind the page — the company or person, with its name, logo and links to its official profiles. This is how Google and AI assistants connect the page to a real, known brand they can recommend.	Organization, Person, WebSite	Good 100%	—
FAQ schema (optional) content work Whether the page labels its question-and-answer content with FAQPage structured data. Informational: since 2023 Google shows FAQ rich results only for government and health sites and no longer shows HowTo results at all, so the markup earns no enhanced result for a commercial page. What AI assistants and 'People also ask' boxes lift is the visible question-and-answer text, measured by the content checks below. A FAQPage block repeating a visible FAQ is harmless; one listing questions the page does not display is not.	FAQPage schema present	Worth knowing	—
Breadcrumb schema quick copy-paste Whether the page describes its position in the site (Home > Category > This page) in structured data. Google then shows that friendly trail in its results instead of the raw address, and understands your site's organization better.	BreadcrumbList found	Good 100%	—

Images

Fix soon

1 critical point — 76%.

Guide

This section answers: Are the page's images described, sized and light enough? Open guide

Words used

Alt text
CLS

data collected 23 Oct 2026

76%2/4 scored points pass. Weakest point: Image dimensions (CLS) (31%).

Help What this section checks: Images affect SEO twice: alt texts make them count as content (and rank in Google Images), and unoptimized files slow the page down — speed is a ranking factor. Every image should have a descriptive alt text and modern sizing attributes. Read more

The 127 images, on four counts

alt text 93 / 12773%

lazy loading 64 / 12750%

width & height set 40 / 12731%

WebP or AVIF 1 / 1271%

Four separate rates over the same images, not four parts of one whole — an image can fail all four independently.

Check points of the J. Images section
Check point	Found	Quality	How to fix / recommendation
Image alt texts content work How many images carry an 'alt text' — a short written description of what the image shows. It is what blind visitors hear, what Google Images indexes, and how search and AI engines know what your pictures contain.	93/127 images have alt text (73%)	Fix soon 73%	How to fix: 93 of 127 images already have a description — finish the job on the remaining 34. For each, write a short sentence saying what the image shows, naturally including the words customers search for when it is honest to do so — this is also how your images appear in Google Images. Every site editor has an 'alt text' field on images.
Lazy loading developer task Whether images further down the page wait to load until the visitor scrolls to them ('lazy loading'). Without it, the browser downloads every image immediately, making the page slower to appear — and speed affects both ranking and sales.	64/127 images use lazy loading	Good 100%	—
Image dimensions (CLS) developer task Whether each image declares its width and height in the code. When it does, the browser reserves the right space before the image arrives; when it does not, the page visibly jumps around while loading — an annoyance Google measures (as 'CLS') and penalizes.	40/127 images declare width and height	Critical 31%	How to fix: 40 of 127 images already declare their size — the remaining 87 still make the layout jump while they load. Ask your developer to add width and height attributes to those image tags too (or update the site's image component to do it everywhere automatically), so the page stops jumping entirely.
Modern image formats developer task Whether images are delivered in modern compressed formats (WebP or AVIF) instead of older JPG/PNG. Modern formats look identical but weigh 30-70% less, so the page loads visibly faster — and page speed influences ranking.	1/127 images served in a modern format	Good 100%	—

Keyword targets: intent vs results

1 informational point, not scored.

Guide

This section answers: Does the page rank for the keywords it says it targets? Open guide

Words used

Meta keywords
Keyword difficulty

data collected 23 Oct 2026

1Informational only — no scored points.

Help What this section checks: The page declares its target keywords in its <meta name="keywords"> tag. Google ignores that tag as a ranking signal — but it is a statement of intent, so this section checks it against reality: how hard each declared keyword is (difficulty 0-100), whether THIS page actually ranks for it in the Google top 100, and whether another page of the site captures it instead. The gap between declared targets and real positions is a ready-made to-do list. Read more

Check points of the M. Keyword targets: intent vs results section
Check point	Found	Quality	How to fix / recommendation
Declared keyword targets quick copy-paste The keywords the page declares as its targets in its <meta name="keywords"> tag. Google ignores this tag as a ranking signal, so it cannot hurt — but writing your targets there lets this report check each one against reality with a real Google search: does the page actually rank for what it aims at?	No meta keywords declared on the page	Worth knowing	Recommendation: Choose the 3-10 searches this page should be found for (the words a customer would type when your page is the answer), and declare them comma-separated in a <meta name="keywords"> tag in the page's code. Google itself ignores the tag, so there is no risk — but this report will then check each declared target against real Google results: how hard it is, whether the page ranks for it, and which page of your site captures it instead.

Section E

Trust and links

Critical

Guide

This section answers: Does the page show it can be trusted, and do other pages vouch for it? Open guide

Who is behind it, its links to and from your other pages, the sites that link to it, and the traffic it earns.

Trust & E-E-A-T

Fix soon

1 critical point — 80%.

Guide

This section answers: Does the page show who wrote it and why it can be trusted? Open guide

Words used

Trust signals: — proof that real, competent people stand behind the site.

data collected 23 Oct 2026

80%4/6 scored points pass. Weakest point: Author and date signals (E-E-A-T) (45%).

Help What this section checks: E-E-A-T (experience, expertise, authoritativeness, trust) is how Google's quality guidelines judge whether a page can be believed — and AI assistants apply the same logic when choosing which sources to cite. This section checks the concrete trust signals: who wrote the page and when, whether an identifiable business with an About and Contact page stands behind it, whether its ratings are backed by real reviews, and whether the practical policies (shipping, returns, guarantee) a buyer checks before ordering are one click away. Read more

Trust markup: what is there, and what is not

Organization properties 2 / 450%

Trust & policy pages 3 / 560%

Missing from the Organization block: address, contactPoint. No link found to: privacy, terms/conditions.

Check points of the E. Trust & E-E-A-T section
Check point	Found	Quality	How to fix / recommendation
Author and date signals (E-E-A-T) content work Whether the page shows who wrote it and when it was published or updated. Google calls this E-E-A-T (experience, expertise, authority, trust): named authors and visible dates make a page look trustworthy — anonymous, undated pages look less citable to both Google and AI assistants.	none	Critical 45%	How to fix: The page is completely anonymous and undated — no author, no byline, no date anywhere in the code. Show who is behind this content and how fresh it is: add a visible author line ('By [name], [role]' — with a short bio if possible) and a visible published or updated date near the top of the content. Trust signals like these cost nothing and make the page more credible to visitors, to Google, and to AI assistants choosing which sources to cite.
About & contact pages content work Whether the page links to an About page (who you are) and a Contact page (how to reach you). Google's quality guidelines explicitly look for both, and AI assistants trust identifiable businesses more than anonymous ones — a shop without a reachable human behind it looks risky to everyone.	links to about page and contact page	Good 100%	—
Organization schema completeness quick copy-paste How completely the structured data describes the organization behind the page: its logo, its official profiles elsewhere (sameAs: social networks, Wikipedia...), and a contact point or address. This is how Google and AI assistants connect the page to one real, known brand — an empty Organization shell connects it to nothing.	Organization schema with logo, sameAs	Good 80%	—
Official profiles (social proof) quick copy-paste Whether the page links to the business's official profiles elsewhere (social networks, video channels...). Independent profiles corroborate that the business really exists and is active — both Google and AI assistants use them to confirm the entity behind the site.	links to facebook.com, instagram.com, pinterest, twitter.com	Good 100%	—
Review & rating integrity content work Whether the ratings the page declares in its structured data are backed by actual reviews. Google requires declared ratings to reflect reviews visible on the page — a star rating with no reviews behind it can be treated as spammy structured data and cost all rich results.	AggregateRating declared, but no Review markup	Fix soon 55%	How to fix: The page declares a star rating (AggregateRating) but marks up no individual review. Show real customer reviews on the page and mark a few of them up with Review schema (author, rating, text), so the declared average is verifiably backed — otherwise Google may ignore or penalize the rating markup.
Policy & trust pages content work Whether the page links to the practical trust pages a buyer checks before ordering: shipping, returns/refunds, guarantee, privacy, terms. Their absence loses hesitant buyers — and AI assistants comparing shops quote exactly these policies ('free returns', 'ships worldwide') when recommending one.	links to: guarantee/warranty, returns/refund, shipping/delivery	Good 100%	—

Links

Good

1 point to improve — 92%.

Guide

This section answers: Do the page's links help visitors and Google find their way? Open guide

Words used

Link words: — the clickable words of a link.
Link ignored: — a mark that asks Google not to count a link.

data collected 23 Oct 2026

92%3/4 scored points pass. Weakest point: Broken link patterns (70%).

Help What this section checks: Internal links tell Google which of your pages matter and spread authority between them; outbound links to credible sources build trust. Descriptive anchor texts ('blue widgets pricing', not 'click here') tell both Google and visitors what the target page is about. Read more

Check points of the G. Links section
Check point	Found	Quality	How to fix / recommendation
Internal links content work How many links this page makes to OTHER pages of your own site. These links guide visitors deeper into the site, help Google discover all your pages, and spread ranking strength between them.	204 internal link(s)	Good 100%	—
External links content work How many links point to OTHER websites. Citing serious outside sources (studies, official references, documentation) makes your content look researched and trustworthy — to readers, to Google, and to AI assistants.	9 external link(s)	Good 100%	—
Anchor text quality content work How many links use vague clickable text like 'click here' or 'read more'. The clickable words of a link tell Google what the destination page is about — vague words waste that signal.	0 generic anchor(s) out of 231 link(s) (0.0%)	Good 100%	—
Broken link patterns developer task How many links lead nowhere — their destination is empty, '#' or a JavaScript action instead of a real page address. These are usually menu buttons coded as links; crawlers treat them as dead ends.	18 suspicious href(s) out of 231 link(s) (7.8%)	Fix soon 70%	How to fix: 18 of the page's 231 links lead nowhere (their destination is empty or '#'). If they are real links, point them at real page addresses. If they only open a menu or accordion, ask your developer to code them as buttons instead of links — visitors see no difference, but crawlers stop wasting time on dead ends.

Backlink profile

Critical

1 critical point — 20%.

Guide

This section answers: Who links to this page, and are those links worth anything? Open guide

Words used

Link from another site: — a link on someone else's site that leads to yours.
Dofollow
Site that links to you: — another website with at least one link to yours.
Spam score

data collected 23 Oct 2026

20%0/1 scored points pass. Weakest point: Backlink volume (20%).

Help What this section checks: Links from other sites remain the strongest off-page ranking factor — each one is a vote of confidence. But quality beats quantity: this section examines who links (domain authority), how (dofollow, anchor text, placement in the page), and whether any links look toxic. Read more

Check points of the I. Backlink profile section
Check point	Found	Quality	How to fix / recommendation
Backlink volume outreach (ongoing) How many other websites link to this page. Each such link ('backlink') works like a vote of confidence — they remain the strongest factor for ranking on Google besides the content itself.	0 backlinks found	Critical 20%	How to fix: No other website links to this page yet, so it has no outside votes of confidence. Start earning some: publish content other sites want to reference (guides, original photos or data), list your business in the serious directories of your industry, and personally propose the page to blogs and partners in your niche. Even a handful of real links makes a difference for a page starting from zero.

Authority & search traffic

Critical

7 critical points — 25%.

Guide

This section answers: How much authority does this page carry, and what traffic does it earn? Open guide

Words used

Page authority
Organic traffic

data collected 23 Oct 2026

25%0/7 scored points pass. Weakest point: Indexed backlink totals (20%).

Help What this section checks: The page's standing in Google's eyes, as AkOOre measures it: its accumulated link authority (rank), how many backlinks the full index counts, how much organic traffic it is estimated to get, and every keyword it currently ranks for. This is the outcome the on-page sections above are trying to improve. Read more

Estimated traffic against measured

Estimated (model) 0.0per month

Measured (Analytics) 028 days

The estimate is a monthly model; the measured figure is a rolling 28-day read from your own Analytics. They share a scale to be compared, not because they cover the same days.

Check points of the K. Authority & search traffic section
Check point	Found	Quality	How to fix / recommendation
Page authority rank outreach (ongoing) The page's overall 'authority' score from 0 to 1000 — a measure of all the link power it has accumulated from other sites, similar to Google's original PageRank. 50+ means real authority; 400+ is a strong page that can compete on hard keywords.	rank 0 / 1000	Critical 25%	How to fix: The page has NO measurable authority yet (rank 0) — the web's link graph barely knows it exists, so it can only rank on searches nobody competes for. Both levers matter from scratch: earn its first real links from outside websites (see the backlink section), and link to it prominently from your own most powerful pages (usually the home page).
Indexed backlink totals outreach (ongoing) The total count of links pointing to this page across the whole web index, and how many DIFFERENT websites they come from. The number of different linking websites is what matters most — each one is a separate vote of confidence.	0 backlink(s) from 0 referring domain(s) (0 main domain(s))	Critical 20%	How to fix: The whole web index counts ZERO links to this page — no outside site has ever voted for it. Start from the accessible end: serious industry directories, partners and suppliers, then propose the page to blogs in your niche. For a page at zero, even 2-3 real linking sites make a measurable difference.
Estimated organic traffic content work An estimate of how many visitors this page receives from Google every month, without any advertising. It is computed from every search the page appears for: how many people make that search, times the share of clicks its position typically gets.	≈ 0 visit(s) / month from Google organic	Critical 20%	How to fix: Google currently sends this page essentially no visitors — it either ranks for nothing, or only beyond position 10 where nobody clicks. The fix starts with content and targeting, not fine-tuning: make the page genuinely answer specific searches (see the keyword sections), then build its authority with links.
Measured visits (Analytics) content work How many visits actually STARTED on this page, and how many of them came from a Google search. Measured by the site's own Analytics, so unlike the estimates above it is not a model of the page — it is the page.	0 visit(s) landed here, 0 from organic search (0%)	Critical 25%	How to fix: Nobody reached this page from a search during the measured period. If it ranks for keywords (the section below), the titles and descriptions are not earning the click; if it ranks for nothing, it is a content problem, not a copy one.
Measured engagement (Analytics) content work The share of visitors who actually engaged with the page instead of leaving straight away. A page can be technically perfect and still lose everyone in the first five seconds; this is the check that can tell.	0% engaged, 0% left without engaging	Critical 35%	How to fix: Most visitors leave this page without doing anything. Before buying more traffic for it, check that the first screen answers the search that brought them, that the page loads fast on a phone (the performance section), and that there is somewhere obvious to go next.
Measured conversions (Analytics) content work The key events — form sends, calls, purchases — credited to visits that landed on this page. The only figure in the report that measures business result rather than visibility.	0 key event(s) from 0 visit(s)	Worth knowing	—
Measured search performance (Search Console) How often Google actually showed this page in its results, at what average position, and how many of those showings earned the click — counted by Google itself, not modelled from third-party data like the estimates above.	1 impression(s), 0 click(s) (0.0% of showings earned the click) at average position 25.0	Critical 30%	How to fix: Google shows this page far more often than people click it — the listing is losing the auction for attention at its own position. That is a title-and-description job: the proposed rewrites in the drafts section exist for exactly this page.
Keyword footprint content work For how many different Google searches this page appears somewhere in the first 100 results. A wide footprint means the page matches many searches — and every improvement to the page lifts all of them at once.	0 keyword(s) in the Google top 100	Critical 20%	How to fix: The page appears for NO search at all in Google's top 100 — it is effectively invisible. Before optimizing details, fix the foundation: enough specific text content on a clearly defined topic (see the content section), then authority through links. A page needs both to enter the top 100 for anything.

Section F

Speed and technical

Critical

Guide

This section answers: Does the page load fast and work for robots? Open guide

Technical & AI readiness (GEO)

Good

1 point to improve — 88%.

Guide

This section answers: Can search and AI engines read this page without running its scripts? Open guide

Words used

Being quoted by AI: — appearing in the answers of ChatGPT, Gemini or Google's AI summary.
Server-rendered

data collected 23 Oct 2026

88%2/3 scored points pass. Weakest point: Script weight (65%).

Help What this section checks: AI answer engines (ChatGPT, Perplexity, Google AI Overviews) can only cite what they can extract: server-rendered text, question-shaped headings, self-contained lists and tables. This section measures how usable the page is as a SOURCE for AI answers — where a growing share of search traffic now starts. Read more

Check points of the F. Technical & AI readiness (GEO) section
Check point	Found	Quality	How to fix / recommendation
Server-rendered content (GEO) developer task Whether the page's text is present directly in its source code, or only appears after JavaScript programs run in the browser. The robots feeding AI assistants (ChatGPT, Perplexity...) mostly do NOT run JavaScript — a page whose text only exists after JavaScript looks empty to them and can never be cited.	~4201 words are server-rendered in the HTML	Good 100%	—
Render-blocking scripts developer task Whether JavaScript files at the top of the page force the browser to stop and download them BEFORE showing anything. Each blocking script delays the moment the visitor sees the page — and that delay hurts both ranking and sales.	0 blocking script(s) in <head>	Good 100%	—
Script weight developer task How many JavaScript files the page loads, and from how many different providers (analytics, chat widgets, ads...). Every script adds download and processing time; pages accumulate them over the years and rarely clean up.	21 external script(s) from 0 domain(s)	Fix soon 65%	How to fix: The page loads 21 JavaScript files — more than the ~10 of a lean page. Review them with your developer: remove tools you no longer use (old analytics, abandoned widgets), combine what remains, and load non-essential ones (chat, social buttons) only after the page has displayed.
Resource hints developer task Whether the page gives the browser 'head start' instructions (preload, preconnect) telling it to fetch critical files early. A nice-to-have speed optimization, not a requirement.	5 resource hint(s) found	Worth knowing	—

Performance (Google Lighthouse)

Critical

2 critical points — 68%.

Guide

This section answers: Is the live page fast and stable enough on a phone? Open guide

Words used

Lighthouse
LCP
CLS
TBT

data collected 23 Oct 2026

68%3/7 scored points pass. Weakest point: Largest Contentful Paint (LCP) (25%).

Help What this section checks: A Google Lighthouse audit of the LIVE page on mobile — the one thing a stored HTML snapshot cannot measure. Page speed and Core Web Vitals (loading, stability, responsiveness) are direct ranking factors, and slow pages lose visitors before the content even shows. Read more

See the technical detail

Lighthouse scores

Performance 54/ 100 Acceptable

SEO 92/ 100 Good

Accessibility 79/ 100 Acceptable

Best practices 100/ 100 Good

Ticks mark Google's own bands: 50 and 90 out of 100.

Core Web Vitals, lab test

Largest Contentful Paint 5.40sgood ≤ 2.5s Poor

Cumulative Layout Shift 0.392good ≤ 0.10 Poor

Total Blocking Time 148msgood ≤ 200ms Good

1 of 3 vitals pass. The three metrics use different units, so each bar is drawn against its own thresholds — the two ticks — rather than on a shared scale.

What to fix first, by the time it saves

Render-blocking requests 2.5 s

Use efficient cache lifetimes 1.3 s

Improve image delivery 1.0 s

Reduce unused CSS 0.5 s

Font display 0.1 s

Lighthouse estimates 5.2 s of loading time available in total. 2 further fixes carry no time estimate: Reduce unused JavaScript (Est savings of 106 KiB); Avoid large layout shifts (1 layout shift found)

Check points of the H. Performance (Google Lighthouse) section
Check point	Found	Quality	How to fix / recommendation
Performance score developer task Google Lighthouse's overall speed score of the live page on a phone (0-100). Speed matters twice: Google uses it in its ranking, and slow pages lose visitors before anything shows — every extra second of loading costs sales.	score 54 / 100	Fix soon 54%	How to fix: At 54/100 the page is workable but slower than it should be on mobile. The usual levers: compress the images and serve them in modern formats, make below-screen images load only on scroll, remove or delay non-essential scripts (old analytics, widgets), and enable caching or a CDN so repeat visits are instant. The detailed measurements below show which of these weighs most — share them with your developer.
Largest Contentful Paint (LCP) developer task How long a visitor waits before the page's main content (usually the big image or headline) appears on a phone. Google's rule of thumb: under 2.5 seconds is good, over 4 seconds is poor — and visitors give up quickly on pages that show nothing.	5.40 s	Critical 25%	How to fix: At 5.4 s the main content is in Google's 'poor' zone (over 4 s) — many visitors leave before seeing anything, and Google penalizes it directly. Fixes for your developer, in order: compress the big top image and load it in priority ('preload'), make the server answer faster (caching, CDN), and remove the scripts that block the page from displaying.
Cumulative Layout Shift (CLS) developer task How much the page visibly jumps around while it loads — text moving as images pop in, buttons shifting under the visitor's finger. Google's rule: under 0.1 is good, over 0.25 is poor.	0.392	Critical 25%	How to fix: At 0.39 the page jumps around badly while loading (Google's 'poor' zone starts at 0.25) — visitors misclick and Google penalizes it. Fixes for your developer: declare width and height on every image and embed so the browser reserves their space in advance, never insert banners above existing content after load, and preload the custom fonts so text doesn't reflow.
Total Blocking Time (TBT) developer task How long the page stays frozen because JavaScript keeps the browser busy — the time during which taps and scrolls don't respond. Under 200 ms is good, over 600 ms is poor.	148 ms	Good 100%	—
Real-user Core Web Vitals developer task What real Chrome visitors measured on this page over the last 28 days, not a simulation. This is the speed data Google uses for ranking.	No real-user data — Google has too few visits to report	Worth knowing	Recommendation: Nothing to fix here: Google only publishes real-user speed for pages with enough traffic to stay anonymous, so this is a statement about audience size, not about speed. The Lighthouse lab numbers above are the measurement to work from until the page gets more visitors.
Lighthouse SEO score developer task Google Lighthouse's checklist of technical SEO basics on the live page: can robots crawl the links, are the title and description present, is the page mobile-friendly, is the text readable on a phone.	score 92 / 100	Good 92%	—
Accessibility score developer task How usable the page is for people with disabilities: enough color contrast to read, descriptions on images, labeled buttons and forms, keyboard navigation. Accessible pages are also easier for search and AI engines to understand — the same labels help both.	score 79 / 100	Fix soon 79%	How to fix: Fix the usual top offenders first: text whose color blends into the background (raise the contrast), images without descriptions, and form fields or icon buttons without a visible label. Each fix helps disabled visitors, and the same information helps search engines and AI assistants understand the page.
Best practices score developer task Google Lighthouse's checklist of general web hygiene: everything served over secure HTTPS, no errors in the browser's console, no outdated technology, images displayed at their intended proportions.	score 100 / 100	Good 100%	—
Top speed opportunities developer task The exact fixes Google Lighthouse itself measured as the biggest speed levers on this page, with the loading time each one is estimated to save. This is the concrete to-do list behind the scores above.	Render-blocking requests (saves ≈2.5 s); Use efficient cache lifetimes (saves ≈1.3 s); Improve image delivery (saves ≈1.0 s); Reduce unused CSS (saves ≈0.5 s); Font display (saves ≈0.1 s); Reduce unused JavaScript — Est savings of 106 KiB; Avoid large layout shifts — 1 layout shift found	Worth knowing	Recommendation: Hand this list to your developer as-is, top item first — it is Lighthouse's own measurement of which fix buys the most seconds on THIS page, so there is no need to guess where to start.

Section G

AI answers and competitors

Guide

This section answers: Do AI assistants quote the page, and who ranks against it? Open guide

AI visibility (questions & answers)

1 informational point, not scored.

Guide

This section answers: When buyers ask an AI assistant, does its answer cite this page? Open guide

Words used

AI citation
Being quoted by AI: — appearing in the answers of ChatGPT, Gemini or Google's AI summary.

data collected 23 Oct 2026

1Informational only — no scored points.

Help What this section checks: A growing share of buyers now asks an AI assistant (ChatGPT, Perplexity...) instead of searching Google. To measure your visibility there, we generated the questions this page should be the answer to, asked a real AI model with web search on, and checked which websites its answers cite. Being cited is the AI equivalent of ranking #1 — this section shows whether you win those citations or your competitors do. Read more

Check points of the C. AI visibility (questions & answers) section
Check point	Found	Quality	How to fix / recommendation
AI answers collection Whether the AI questions/answers of this page (real AI-assistant answers to 5 user questions generated from the page content) were fetched yet.	Not fetched yet — the task runs once per page when its promotion is enabled and an HTML snapshot is stored	Worth knowing	Recommendation: Enable promotion for this page (pages list, Promotion column) to trigger the one-time data collection.

Competitive landscape

2 informational points, not scored.

Guide

This section answers: Who competes with this page, and can it beat them? Open guide

Words used

Google results page: — the page Google shows after someone searches.
Authority

data collected 23 Oct 2026

2Informational only — no scored points.

Help What this section checks: Your competitors here are measured three ways: the sites that get links from the same sources as you (they compete for the same audience and the same links), the sites that rank on Google for the same keywords as yours (they take the clicks you want even without sharing your link sources), and the sites that AI assistants cite instead of you for the questions this page should answer. Comparing their strength with yours shows whether you are outgunned or can win — and which competitors are beatable first. Read more

Check points of the L. Competitive landscape section
Check point	Found	Quality	How to fix / recommendation
Competitors collection Whether the competitor domains of this page (sites sharing its backlink sources) have been collected yet.	No competitor data returned by our estimation system	Worth knowing	—
Competitors on your Google results content work The domains that rank in Google for the same keywords as this site, ranked by how many keywords you share. Unlike the link-space competitors above, these are found on the result pages themselves — they take the clicks you want even when they share none of your link sources.	myfigurecollection.net (1 shared keyword(s), avg position 3, rank 524); specfictionshop.com (1 shared keyword(s), avg position 1, rank 354); miraicollectibles.com (1 shared keyword(s), avg position 28, rank 265); otakuhobbitoysph.com (1 shared keyword(s), avg position 39, rank 246); clubhousestatues.com (1 shared keyword(s), avg position 20, rank 194) — 15 of 19 are weaker than your site (rank 240/1000)	Worth knowing	Recommendation: Search Google for your own target keywords and study how myfigurecollection.net presents its pages in the results (titles, descriptions, rich snippets) — it shares the most keywords with you. Start by out-writing the competitors weaker than your site: better titles and content on the shared keywords is enough to pass them, no new links needed.

All stored competitors (19)

Help How to read these tables: Competitors by shared link sources — sites that receive links from the same websites that link to you. Sharing link sources means you compete for the same audience. "Websites linking to you both" counts how many sources you share: the higher, the more direct the competition. Competitors on your Google results — sites that rank in Google for the same keywords as yours, found on the result pages themselves. "Keywords you share" counts the searches where you both appear; "its average position" is where the competitor typically shows up on them; "its monthly Google visits" estimates the traffic its whole domain earns from Google. Its authority (/1000) — the competitor's overall link power, drawn as a bar next to the number. vs you — the same authority compared with yours: beatable is weaker than you (overtake it with better content and a few links), close fight is up to twice your authority (winnable with focused work), out of your league is far above (do not chase it head-on; target its weaker keywords instead). Signals — links to you: this competitor already links to your page, a warm contact for more links; wins AI citations: AI answers cite this site for questions your page should answer (see the AI visibility section). Read more

19 competitors identified

15 beatable now (weaker than you)

0 already link to you

0 win AI citations against you

Your reference: your site's authority is 240/1000 — every "vs you" verdict below compares against it.

Competitors on your Google results (19 of 19)

CSV XLSX

Competitor website	Its authority /1000	vs you	Keywords you share	Its average position	Its monthly Google visits	Signals
myfigurecollection.net	524	out of your league	1	pos 3	~216,477	—
specfictionshop.com	354	close fight	1	pos 1	~33,184	—
miraicollectibles.com	265	close fight	1	pos 28	~3,297	—
otakuhobbitoysph.com	246	close fight	1	pos 39	~781	—
clubhousestatues.com	194	beatable	1	pos 20	~4,544	—
bucketandshovel.com	185	beatable	1	pos 22	~17,583	—
anitoysgk.com	173	beatable	1	pos 36	~1,168	—
comic-concepts.com	172	beatable	1	pos 60	~8,018	—
oneofakindinc.com	169	beatable	1	pos 41	~416	—
jidouartstudio.com	75	beatable	1	pos 47	~1,487	—
gilliancampbell.tv	50	beatable	1	pos 65	~7,631	—
marounssupermarket.com	36	beatable	1	pos 50	~5,789	—
diecastfigures.com	0	beatable	1	pos 71	~49	—
epicfigurestore.com	0	beatable	1	pos 29	~25	—
navytoysinternational.com	0	beatable	1	pos 17	~1,547	—
simplyuniqueartstudio.com	0	beatable	1	pos 16	~2	—
unique-artstudio.com	0	beatable	1	pos 14	~1	—
uniqueart-studio.com	0	beatable	1	pos 10	~10	—
uniqueartworld.com	0	beatable	1	pos 43	~141	—

This page scores 77% — acceptable, with 12 critical points to fix first.

What to fix first

How to use this plan

Do these today — quick wins (1)

1. Fix first — critical (12)

2. Then improve (8)

3. Opportunities from the data (5)

How your page scores

Ready for AI answers

What to change, highest value first

What Google reads on the page

Head & meta tags

Content structure & quality

Structured data (SEO & GEO)

Images

Keyword targets: intent vs results

Trust and links

Trust & E-E-A-T

Links

Backlink profile

Authority & search traffic

Speed and technical

Technical & AI readiness (GEO)

Performance (Google Lighthouse)

AI answers and competitors

AI visibility (questions & answers)

Competitive landscape

All stored competitors (19)

Competitors on your Google results (19 of 19)

Add to your ToDo list

Send feedback