Page SEO/GEO report — https://www.originaluniqueart.com/ — generated on Nov. 22, 2026, 5:13 p.m. by AkOOre
← Audited PagesOverviewPage SEO/GEO report · / · 20 Nov 2026
This page scores 77% — acceptable, with 10 critical points to fix first.
26 of the 44 scored check points pass and 8 need improvement. On the page itself, the weakest area is Structured data (SEO & GEO) (76%) and the strongest Links (98%). 1 section still waits for its data — the collection runs every minute.
- 77%
- Overall quality
- 85%
- GEO / AI readiness
- —
- Page speed
- 0/1000
- Page authority
- 0/ month
- Organic traffic
- 10
- Critical issues
Section A · The work
What to fix first
4 recommendations, worst first.
Words used
- Quick win
- Critical
4recommendations to work through
How to use this plan
- Start with the "quick wins" list. Those are minutes of work each, in your page editor — no writing, no developer. Most of them even have the finished code waiting in the Ready-to-paste fixes section below: copy the block, paste it into the page, done. Go to the ready-to-paste fixes
- Then take the "Fix first" 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 the Refresh button at the top of the report. 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 2 — 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 1 — 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.
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.
Do these today — quick wins (1)
- Open Graph tags
2. Then improve (4)
-
Question-form headings (GEO)
content work
What to do: Rewrite a few section headings as the real questions your customers ask — 'How are the paintings made?', 'How long does delivery take?' — and answer each one directly in the very first sentence below it (details can follow after). This question-plus-direct-answer format is exactly what Google's 'People also ask' boxes and AI assistants lift into their answers, with a link to you as the source.
-
Open Graph tags
quick copy-paste
What to do: The page already has og:title, og:description, so shared previews partly work — but og:image is still missing, and a preview without an image is what costs the most clicks: chat apps and social feeds show image-less links as a bare grey line. Complete the set in the page's <head> — most site platforms and SEO plugins can fill these automatically.
-
Heading hierarchy
content work
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.
-
Text-to-HTML ratio
developer task
What to do: Only 9.5% 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.
Section B · Standing
How your page scores
77% overall, 10 critical points.
Words used
- Check point
- Critical
77%Overall quality: Acceptable
- 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.
This page scores 77% overall — acceptable: 26 of the 44 scored check points pass, 8 need improvement and 10 are critical. On-page, the strongest area is G. Links (98%) and the weakest is D. Structured data (SEO & GEO) (76%). GEO / AI readiness is at 85% — 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: Image dimensions (CLS) (8%), Backlink volume (20%), Estimated organic traffic (20%) — the action plan below is ordered accordingly.
https://www.originaluniqueart.com/ · Snapshot taken 20 Nov 2026 · Language en · 12/13 sections have data
See every recorded day
Nov 21: 79% Fix soon → Nov 22: 77% Fix soon
Applied some fixes on your page? Mark them done in the action plan above, 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 · Copy & paste
Ready-to-paste fixes
1 fix ready to paste.
Words used
- JSON-LD
- Meta description
1ready-to-paste fix
Main entity schema (OnlineStore)
Paste into the page's <head>. It tells Google and AI assistants what this page IS, which qualifies it for enhanced results. Replace every [TODO ...] before publishing.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "OnlineStore",
"name": "Original One-of-a-Kind Art for Sale | OriginalUniqueArt.com",
"description": "OriginalUniqueArt.com - Originals by our exclusive artists — each sold once, never repeated. Claim your one-of-a-kind piece before someone else does.",
"url": "https://originaluniqueart.com/en/",
"image": "https://www.originaluniqueart.com/static/flags/gb.gif"
}
</script>
Section D · On the page
Head & meta tags
1 point to improve — 96%.
Words used
- Meta description
- Main version
- — the address you tell Google is the real one when several pages look alike.
- Open Graph
data collected 20 Nov 2026
96%8/9 scored points pass. Weakest point: Open Graph tags (67%).
| 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. |
"Original One-of-a-Kind Art for Sale | OriginalUniqueArt.com" (59 chars) |
Good
|
— |
|
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. |
"OriginalUniqueArt.com - Originals by our exclusive artists — each sold once, never repeated. Claim your one-of-a-kind piece before someone else does." (149 chars) |
Good
|
— |
|
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/en/ |
Good
|
— |
|
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. |
No robots meta (default: index, follow) |
Good
|
— |
|
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="en" |
Good
|
— |
|
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
|
— |
|
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
|
— |
|
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 |
Fix soon
|
How to fix:
The page already has og:title, og:description, so shared previews partly work — but og:image is still missing, and a preview without an image is what costs the most clicks: chat apps and social feeds show image-less links as a bare grey line. Complete the set in the page's <head> — most site platforms and SEO plugins can fill these automatically.
|
|
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
|
— |
Section E · On the page
Content structure & quality
3 points to improve — 85%.
Words used
- H1
- Heading hierarchy
data collected 20 Nov 2026
85%4/7 scored points pass. Weakest point: Question-form headings (GEO) (55%).
The heading structure, in page order
1 level is skipped — a gap in the outline, marked above where it happens.
| 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: "Exclusive artworks,from artists youwon't findanywhere else." |
Good
|
— |
|
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. |
38 heading(s), 7 H2, levels skipped |
Fix soon
|
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. |
0 question heading(s) |
Fix soon
|
How to fix:
Rewrite a few section headings as the real questions your customers ask — 'How are the paintings made?', 'How long does delivery take?' — and answer each one directly in the very first sentence below it (details can follow after). This question-plus-direct-answer format is exactly what Google's 'People also ask' boxes and AI assistants lift into their answers, with a link to you as the source.
|
|
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. |
~2711 words of visible text |
Good
|
— |
|
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. |
9.5% (18288 text bytes / 192119 HTML bytes) |
Fix soon
|
How to fix:
Only 9.5% 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. |
19 list(s), 0 table(s) |
Good
|
— |
|
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, article, nav, header, footer |
Good
|
— |
AkBot will be asked