Tencent Hy

The audited page has no meta description.

The title and description are the text someone reads in a search result before deciding whether to click. Right now the sampled pages don't provide it.

Add <meta name="description" content="…"> with a one- or two-sentence summary of the page. Without it, search engines and link previews build a snippet from whatever page text they pick.

Title "Tencent Hy" is 10 characters, under this audit's 15-character review point (a heuristic, not a Google minimum).

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Make the title descriptive enough to identify the page topic and purpose without padding it to a target count.

There is no meta description, so its length cannot be measured.

The title and description are the text someone reads in a search result before deciding whether to click. This check does not apply to the features observed in this sample.

The description presence check covers the missing element. Review length once a description exists.

Fewer than two indexable pages with a title were sampled, so titles can't be compared.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Link your main pages from the homepage so crawlers (including this one) can find them.

Title found: "Tencent Hy"

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title "Tencent Hy" says more than the site name.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

The sitemap contains zero <loc> entries.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. Right now the sampled pages don't provide it.

Populate it with your real page URLs — an empty sitemap tells Google you have nothing to index.

The homepage has no canonical link.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Add <link rel="canonical"> (Next.js: metadata.alternates.canonical). It consolidates ranking signals when the page is reachable under several URLs (with/without query params, trailing slash…).

robots.txt doesn't declare the sitemap.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Add "Sitemap: https://hy.tencent.ai/sitemap.xml" to robots.txt so every crawler finds it without Search Console.

The robots.txt URL returned HTML instead of a readable policy.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Serve a plain-text robots policy or return a proper missing-file status.

Googlebot policy could not be established from the robots response.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Make /robots.txt reachable and return a complete plain-text policy.

The page declares no canonical URL, so there is nothing to validate.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Add <link rel="canonical" href="…"> pointing at the absolute, preferred URL of the page.

The audited page has about 0 words of main content (navigation, header and footer excluded).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. Right now the sampled pages don't provide it.

Add substance: what the site is, who it's for, what problems it solves. This audit measures visible HTML; it does not measure rankings, traffic, or content originality. Note: if your content renders only via client-side JS, crawlers without JS (and this checker) can't see it — prefer server rendering.

1 sampled page(s) expose fewer than 30 publisher words and an empty application root with script references.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Server-render or statically render the page's primary content. Google can render JavaScript, but rendering can fail or be delayed and other crawlers may not execute it.

• https://hy.tencent.ai/

Visible text is 0.0% of the HTML markup (scripts and styles excluded).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Text-to-HTML ratio is not a ranking factor, but a very low value often means deeply nested markup or content that only appears after JavaScript runs. Check the source-content checks before changing anything.

Readability is estimated only for English; the page declares lang="zh-CN".

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Nothing to change for this check.

Need both a <title> and an H1 to compare them.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.

Add whichever is missing — the metadata and headings checks name it — then this check confirms the two describe the same topic.

Only one page was sampled, so there is nothing to compare.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Link your main pages from the homepage so the audit can sample and compare them.

No og:description tag and no meta description to fall back on.

This is what your link looks like when someone drops it into a chat or a feed. Right now the sampled pages don't provide it.

Add og:description. It is the preview text under shared links.

No og:image tag.

This is what your link looks like when someone drops it into a chat or a feed. Right now the sampled pages don't provide it.

Add a 1200×630 og:image. Without one, a shared link renders as plain text in most apps. Next.js generates one from opengraph-image.tsx.

No og:title tag. Most apps fall back to the <title> ("Tencent Hy") for the preview headline.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Add og:title when the share headline should differ from the search title, or to control the headline on platforms that do not fall back.

No twitter:card tag.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Add <meta name="twitter:card" content="summary_large_image">. X falls back to Open Graph for the rest, but the card type itself must be declared.

Neither og:url nor og:type is set.

This is what your link looks like when someone drops it into a chat or a feed. It is there, but weaker than this check expects.

Add og:url (canonical URL) and og:type ("website" for the homepage).

No og:image tag was found, so there is no image URL to fetch and verify.

This is what your link looks like when someone drops it into a chat or a feed. This check does not apply to the features observed in this sample.

Add <meta property="og:image" content="…"> with an absolute URL. This check then confirms the file actually loads.

No og:image tag was found, so its declared dimensions cannot be reviewed.

This is what your link looks like when someone drops it into a chat or a feed. This check does not apply to the features observed in this sample.

Add the og:image tag first, then declare og:image:width and og:image:height alongside it.

No og:site_name tag.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add it. Share cards use it to label the publisher; consistent naming also gives this audit a measurable entity signal. It does not measure or guarantee citations, rankings, or traffic.

No JSON-LD structured data on the homepage.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.

No Organization, WebSite or Person schema found.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Add an identity node so search engines and AI assistants can attribute your content to a real entity.

No JSON-LD blocks were found, so there is no syntax to validate.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.

No inner pages crawled.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Not applicable until inner pages exist.

No content-specific schema (Article, Product, FAQPage…) detected.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.

The audited page has no <h1>.

Headings are the outline every parser and screen reader follows to find the answer. Right now the sampled pages don't provide it.

Add one <h1> stating what the page is about, usually the hero headline. Search engines, screen readers and answer engines use it as the page's main heading.

No H1 exists to check for uniqueness.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing main heading.

The page has no headings, so there is nothing further to assess.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.

No H1 text exists to inspect.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing main heading.

The page has no headings, so there is nothing further to assess.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.

The page has no headings, so there is nothing further to assess.

Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.

The H1 presence check covers the missing headings. Add an H1 and descriptive H2 sections.

All inspected element IDs are unique within their documents.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

No visible <img> elements on the audited page (hidden, presentational and 1×1 tracking images are not counted).

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Nothing to change here. Any image you add later needs alt text that describes it, so this check starts scoring then.

No visible <img> elements to measure on the audited page.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Nothing to change here. Give future images explicit width and height attributes so the browser can reserve their space.

No raster images with a recognizable file extension were found.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Nothing to change here. If images arrive later, serve WebP or AVIF alongside PNG/JPEG.

Only 0 visible image(s) on the page, too few for lazy loading to change the initial load.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.

The homepage links to only 0 distinct internal page(s).

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.

Link generously to your key pages from the homepage — it's how crawlers discover them and how PageRank flows.

No internal links were probed.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add internal links from your homepage.

No links were found on the audited page.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.

Link to your main pages from the homepage. Crawlers and readers both need a path in, and this check then reviews the anchor text.

No same-page fragment links to check.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. This check does not apply to the features observed in this sample.

Keep section links connected to stable IDs.

No placeholder links on the audited page.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

All target="_blank" links carry rel="noopener".

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

The viewport limits zoom: "width=device-width,initial-scale=1,user-scalable=0,viewport-fit=cover".

Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.

Remove user-scalable=no and any maximum-scale below 2. People with low vision need to zoom to at least 200% (WCAG 1.4.4). Recent iOS ignores the restriction, but Android browsers apply it.

Only 0 image(s) on the page, too few for responsive image markup to change what phones download.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Nothing to change here. When the page carries several images, give them srcset and sizes so phones fetch smaller files.

No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Check computed font sizes in a browser across mobile widths.

No source-level interactive controls were found.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Inspect browser-rendered controls separately if the page adds interactions with JavaScript.

No ARIA ID references found in the sampled HTML.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Verify rendered accessibility separately.

Viewport configured: "width=device-width,initial-scale=1,user-scalable=0,viewport-fit=cover".

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

No hreflang tags — fine for single-language sites.

The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.

Only add hreflang if you publish the same content in multiple languages/regions.

Language comparison is not supported for lang="zh".

The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.

Nothing to change for this check. Confirm the lang attribute names the language most of the page is written in.

Language declared: lang="zh-CN".

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

No apple-touch-icon link.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.

Favicon declared via <link rel="icon"> (https://cdn-front.hy.tencent.ai/logo.svg).

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.

Web manifest links and parses correctly.

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.

theme-color is "#f9f9f9".

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.