Yang Tang - Academic Profile

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.

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: "Yang Tang - Academic Profile"

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 is 28 characters, inside this audit's 15–60 review range.

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 "Yang Tang - Academic Profile" 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.

No sitemap found (checked https://tang1693.github.io/sitemap.xml → 404).

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.

Publish a sitemap.xml and submit it in Google Search Console. Next.js: export from app/sitemap.ts — it's ~10 lines.

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…).

No sitemap was found, so there are no submitted URLs to compare against.

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.

The sitemap check covers the missing file. Once one exists, this check confirms the URLs it lists are indexable.

robots.txt is absent. A missing policy permits crawling by default.

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.

Optional: publish a robots policy to advertise a sitemap or restrict selected paths.

No sitemap was reachable, so its contents cannot be validated.

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.

Publish /sitemap.xml with your canonical URLs. This check then validates the XML and the URLs it lists.

No sitemap was reachable, so robots.txt has nothing to point at.

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.

Publish the sitemap first, then add a Sitemap: line to robots.txt naming its absolute URL.

Flesch reading ease ≈ 17 — very difficult.

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.

Shorten sentences and prefer plain words. Aim for 50–70 for a general audience.

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.

Only one distinct content page was sampled, so repeated discovery copy cannot 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.

Sample at least two substantial URLs so repeated descriptions, H1s, and publisher text can be checked.

No recognized empty JavaScript application shell on 1 sampled page(s). The entered page exposes 1128 publisher word(s).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

The audited page has about 1128 words of main content.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

Text-to-HTML ratio is 68.2%.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

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> ("Yang Tang - Academic Profile") 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.

H1 found: "Yang Tang"

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

Nothing to do here.

Exactly one H1 on the homepage.

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

Nothing to do here.

Heading hierarchy is sequential across 10 headings.

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

Nothing to do here.

H1 reads "Yang Tang".

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

Nothing to do here.

10 headings, averaging 2.1 words — descriptive.

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

Nothing to do here.

9 H2 section(s) structure the page.

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

Nothing to do here.

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 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.

1 of 1 links have descriptive text or labels.

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.

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.

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 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.0".

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

Nothing to do here.

The viewport lets users zoom.

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

Nothing to do here.

2 source controls have detectable names. Browser accessibility and CSS visibility were not tested.

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 declared: lang="en".

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.

Declared language (en) matches detected content language.

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 favicon found: no <link rel="icon"> tag, and /favicon.ico returned 404.

These icons are what appear in browser tabs, bookmarks and search results. It is there, but weaker than this check expects.

Add one — the browser tab, bookmarks and Google's mobile results all show it. A missing favicon reads as unfinished.

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.

No web manifest linked.

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.

Optional, but a manifest.json enables install prompts and better mobile integration.

No theme-color meta 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 <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.