MacThru — Focused Utility Apps for Mac

Title found: "MacThru — Focused Utility Apps for Mac"

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 38 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 "MacThru — Focused Utility Apps for Mac" 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.

Meta description found: "Discover MacThru utility apps for text capture, Mac controls, Safari streaming enhancement…"

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.

Description is 148 characters and inside this audit's 70–160 preview 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.

All 2 indexable sampled pages have distinct titles.

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.

8 sampled URL(s) have conflicting indexability signals: https://www.macthru.com/about/ (canonical https://www.macthru.com/); https://www.macthru.com/store/ (canonical https://www.macthru.com/); https://www.macthru.com/textly/ (canonical https://www.macthru.com/); https://www.macthru.com/easily/ (canonical https://www.macthru.com/); https://www.macthru.com/cine-5-1-audio-for-netflix/ (canonical https://www.macthru.com/); https://www.macthru.com/tejora/ (canonical https://www.macthru.com/); https://www.macthru.com/volora/ (canonical https://www.macthru.com/); https://www.macthru.com/legal/ (canonical https://www.macthru.com/).

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.

Keep submitted sitemap URLs successful and intended for indexing. Remove accidental noindex, list the preferred canonical URLs, and replace stale redirecting entries. A useful page does not have to appear in a sitemap.

• https://www.macthru.com/about/
• https://www.macthru.com/store/
• https://www.macthru.com/textly/
• https://www.macthru.com/easily/
• https://www.macthru.com/cine-5-1-audio-for-netflix/
• https://www.macthru.com/tejora/
• https://www.macthru.com/volora/
• https://www.macthru.com/legal/

One canonical declaration found.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No conflicting noindex and cross-page canonical instructions.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No meta-refresh redirect.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

No soft-404 pattern on sampled HTTP 200 pages.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

Canonical is a valid https URL. Its host is checked by the canonical consistency check.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.

Nothing to do here.

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.

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.

Not enough English prose to estimate readability (it needs about 100 words in three or more sentences).

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.

Fewer than two indexable sampled pages carry more than 50 words of main content, so there is nothing to compare.

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.

No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 0 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.

og:image:width / og:image:height are missing.

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.

Declare them (1200×630 recommended) so platforms render the preview immediately on first share instead of after re-scraping.

og:title: "MacThru — Focused Utility Apps for Mac"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:description: "Focused utility apps for Mac, including text capture, quick controls, Safari streaming enh…"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image is set: "https://www.macthru.com/assets/social/macthru.png"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image returns 200 (image/png).

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:url and og:type ("website") are set.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

twitter:card is "summary_large_image".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:site_name: "MacThru".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

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

All 1 JSON-LD block(s) parse cleanly.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

1/9 inner pages have breadcrumb schema.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.

Nothing to do here.

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

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.

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

Not enough text on the page to tell which language it is written in.

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

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.

Favicon declared via <link rel="icon"> (/assets/logo-C-f8J9gb.svg).

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

Nothing to do here.

apple-touch-icon is declared.

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 "#f5f7fc".

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

Nothing to do here.