Yana Immis · Independent SEO review

Website SEO Checkup

What the audit found, where it appears, and what each finding means for visitors and search engines.

Yana Immis advising students during an international education visit in Sri Lanka
Report sections
Finding key Good Needs improvement Serious issue
2

Needs improvement: Crawlability, URLs & 404 behavior

Good: Fresh crawl: all sitemap pages loaded

What search engines can reach

A September 3 crawl checked every URL listed in the public XML sitemap.

198 / 198sitemap URLs returned 200
0broken sitemap URLs found

What “returned 200” means: every page currently listed in the site’s sitemap loaded normally when tested. None led to a missing or broken page, so search engines had a working path to every listed URL.

Good: Secure address and redirectWhich address visitors and search engines receive

The site uses the secure https://www domain as its main host and redirects the unsecured version to it. http://yanaimmis.com/redirects tohttps://www.yanaimmis.com/Without this redirect, search engines could treat the host versions as separate copies and divide their ranking information. The current redirect keeps visitors and search engines on one clear, secure host; no change is needed for this host redirect.

Good: Robots file and XML sitemap

The site has a working robots file with crawler instructions and an XML sitemap listing its public pages. Without the sitemap, new or deeply linked pages can be harder to discover; without the robots file, crawlers lose the site’s explicit instructions. Both are currently available and help search engines crawl the intended pages, although neither raises rankings by itself.

Needs improvement: 31 archive URLs in the sitemap

The site currently lists 21 category pages and 10 tag pages in its sitemap, making every archive available for search engines to discover and assess. Archives with only repeated links may add little value, while clearly described archives can help visitors and search engines understand each topic. Reviewing the less useful archives could reduce repetitive pages competing for attention without removing the article library. See every archive URL.

Needs improvement: Missing-page behaviorWhat visitors see when a page is missing Small screenshot of the homepage displayed at a nonexistent Yana Immis URLMissing address displays the homepage

If someone opens an address for a page that no longer exists, this site sends the correct HTTP 404 missing-page signal to search engines but displays the homepage to visitors without changing the address. Search engines can recognize that the page is missing; visitors may think they reached the wrong place because they are not told what happened. You can decide whether the current homepage fallback or a dedicated missing-page message is more useful for visitors.

Resources: complete 198-page crawl table, HTTP observations, and every category and tag archive.

Related improvement plan: choose the primary routes and verify their redirects and decide which archives remain searchable.

6

Needs improvement: Sharing, site identity & structured data

Browser icon & site identity

Programs Abroad for Any Age — Yana Immis
Needs improvement: Current favicon

The site has a valid 32×32 WebP favicon that can appear in browser tabs, bookmarks, and Google results. A 144×144-pixel square source is recommended because it retains more detail when a browser or device displays the icon larger; the current 32×32 image has fewer pixels to enlarge. This is a visual-quality improvement, not a ranking factor.

Current Yana Immis favicon enlarged from 32 by 32 pixelsCurrent favicon · enlarged for inspection

Needs improvement: Google search appearance

Needs improvement: Share image & share text

The site supplies information that messaging apps and social platforms use to create link previews. People may see the resulting title, description, and image when someone shares a Yana page through WhatsApp, Facebook, LinkedIn, X, or another service that supports previews. The examples below show how the homepage can appear on LinkedIn and X. Without these fields, each service may choose page text and images itself or show only a plain link without an image or description.

What this table shows: the hidden page fields each service reads to build the visible shared-link previews above. This deeper sharing review covered the homepage and 18 main non-blog pages—the site’s core service, information, contact, and application routes. Blog posts and archive pages also matter, but this audit’s wider 198-page crawl checked their search titles and descriptions rather than every sharing field.

Platform fieldLive statusWhat was found
Facebook & LinkedIn · preview wordsog:title / og:descriptionPresentThe homepage and all 18 checked main non-blog pages provide the bold title and supporting text shown under the shared image.
Facebook & LinkedIn · link destinationog:url / og:typePresentEvery checked page identifies the address opened when someone clicks its preview and labels itself as a website page.
Facebook & LinkedIn · preview pictureog:imageHTTP image URLsAll 19 pages provide the large image shown above the preview text, but every address begins with insecure http://. Secure image addresses could make preview loading more reliable.
Screen readers · share-image descriptionog:image:altMissing on 19 pagesA live September 4 check found no image-description field on any of the 19 main pages. This does not affect rankings, but a screen-reader user may not receive a useful description of the image in a Facebook or LinkedIn preview.
X · card shapetwitter:cardPresentAll 19 checked pages request X’s compact summary card. This is valid; it gives the image less space than X’s large-image card.
X · preview words, picture & linkX title / description / image / URLPresentAll checked pages provide the visible X preview content, so X does not have to guess it from the page.
Platform preview testNot measuredNo Facebook, LinkedIn, or X preview test was supplied. The fields exist, but their final appearance and any platform caching remain unconfirmed.

Share image and text conclusions

Serious issue: Preferred URLs & duplicate routes

The checked pages have preferred-URL tags, which tell Google which address should represent the content. Both addresses in each combination below are live, so Google receives competing signals and must decide which address to show.

Needs improvement: One page appears at two routes
/study-abroaddeclares the preferred URL as/

Both routes are currently crawlable, while the preferred-URL tag points to the root. One consistent address would make the site’s choice clearer and keep links and ranking information together.

Serious issue: Two pages claim the homepage role

Both pages are currently public and each declares itself preferred. This can divide links and ranking information. One clear homepage address would give visitors, search engines, and reports the same destination.

Needs improvement: Two application routes
Small screenshot of the Application pageApplicationSmall screenshot of the Apply to University pageApply to University

Both application pages are currently public and serve nearly the same purpose. A single clear route could prevent them competing for the same searches and make the current form obvious to visitors.

Needs improvement: Structured business information

The site currently contains WebSite, Organization, and LocalBusiness records that describe the site and business to search systems. Some details are incomplete or split between records; more consistent information could make the business relationship easier to interpret. Structured data can support some enhanced search displays, but it does not directly raise rankings. Open the captured structured data.

Ubersuggest SEO opportunities showing five suggested topics, 13 low-word-count pages, eight pages with duplicate titles, six pages with duplicate descriptions, two pages without descriptions, and 45 pages with long titles.

Needs improvement: Ubersuggest audit snapshot

Within Ubersuggest's smaller audit sample, the saved audit flagged 45 long titles, 13 low-word-count pages, 8 pages with duplicate titles, 6 pages with duplicate descriptions, and 2 pages without descriptions. The separate 33-page count above comes from the full 198-URL crawl. These are screening flags, not Google penalties. They identify pages where a search result may be repetitive, unclear, or based on limited page text.

Main-page metadata inventory

This inventory covers the homepage plus 18 non-blog core routes from the sitemap. It intentionally does not repeat the 148 article pages, 21 category archives, or 10 tag archives.

Resources: complete 198-page metadata table, September 3 live metadata inventory, full title and description crawl, live icon observations, sitemap inventory, and browser and structured-data observations.

Related improvement plan: titles and descriptions, sharing and structured data, and preferred URLs.

3

Serious issue: Headings, images & accessibility

The page structure exposed to search engines and people using assistive technology.

Serious issue: Heading structure

The site currently has inconsistent heading structure: the homepage contains an empty H3, three H1 headings—“Yana Immis,” “YANA IMMIS,” and “Study Abroad”—and no H2 headings. Across the sitemap, 68 of 198 pages have more than one H1 and 18 have no H1. This is not a Google penalty, but a clearer hierarchy could make each page’s main topic and sections easier for visitors, screen readers, and search engines to understand.

Current homepage outlineH3 emptyH1 Yana ImmisH1 YANA IMMISH1 Study AbroadH2 none

Needs improvement: Image accessibility

The homepage currently has 166 rendered images, and every image has an alt attribute. That gives the site a usable accessibility foundation. Four descriptions are empty; this is correct for decorative images but would hide meaningful images from screen-reader users. Some linked gallery items also lack clear names, so a screen reader may announce only “link.” These gaps could keep visitors without sight from understanding some of the visual content.

Resources: every crawled page heading and browser structure and accessibility observations.

Related improvement plan: heading structure and linked images and accessibility.

5

Needs improvement: Content, search titles & descriptions

What the public content library covers and how its pages appear in search.

Good: Public content library

The site currently has a broad public library: 148 articles, 19 core pages, 21 category pages, and 10 tag pages. It covers country choice, universities, funding, visas, accommodation, student experiences, and recent topics such as visa rejection patterns and study-permit approvals.

Needs improvement: Connections between related pages

Success stories, FAQs, institution pages, and destination pages can answer questions people ask before choosing a program or consultant. Page count alone does not improve rankings; stronger connections between related pages could make the library easier to navigate and understand.

Good: Pages attracting external links

Moz estimates that the IELTS guide and homepage have accumulated the strongest external-link authority among the pages it listed. This suggests that practical, evergreen guidance already gives other websites something worth referencing. Links from relevant, trustworthy websites can help people discover a page and can help search engines assess its reputation.

PageMoz Page Authority
IELTS tips and tricks27
Homepage26
GMAT preparation24

How to read this: Page Authority is Moz’s comparison score, not a Google metric or a ranking guarantee. The complete Moz table in Sources lists seven pages.

Needs improvement: Moz authority and visibility estimates

Domain Authority
7
Linking websites
110
Ranking keywords
84

Domain Authority 7 is Moz’s 1–100 estimate of how competitive the whole domain may be. It is modest, but Google does not use this score directly.

110 linking websites means Moz found links from 110 distinct domains. Relevant links from different reputable sites can strengthen discovery and reputation more than repeated links from one site.

84 ranking keywords means Moz estimates that the site appears within its tracked search-result range for 84 terms. It does not show how many qualified visitors or inquiries those appearances produced.

Examples in Moz’s linking-domain list include medium.com (Authority 95), entrepreneur.com (92), and meetup.com (91). A high Moz score for a linking website does not prove that a particular link is still active, relevant, or valuable. Moz did not display a Spam Score, so no conclusion is drawn from that field.

Resources: sitemap inventory, dated article sample, the live blog archive, complete Moz tables, and the live Moz Domain Analysis.

Related improvement plan: content journeys, regulated advice, and article pathways.

1

Serious issue: Performance & visitor experience

Saved real-user and lab measurements for loading speed, page weight, and responsiveness.

Serious issue: Homepage page weight

451,664 BUncompressed homepage HTML
55Script elements in server HTML
245Image elements in server HTML
79Lazy-loading references

The live homepage currently sends substantial HTML and contains many scripts and images. These counts do not determine an SEO score by themselves, but more page resources can increase the work a phone must complete before the page becomes useful. Reducing unnecessary first-view weight could help visitors see and use the page sooner.

GTmetrix CrUX snapshot showing a failed Core Web Vitals assessment, LCP of 3.8 seconds, CLS of 0.11, FCP of 2.7 seconds, TTFB of 1.1 seconds, and no INP result.

Serious issue: GTmetrix real-user snapshot

The field snapshot shows that visitors often wait longer than Google’s recommended limits for the page to become useful. The largest delay is the main content: 3.8 seconds instead of the 2.5-second target. The first visible content also misses its target (2.7 seconds instead of 1.8), while layout movement is only slightly above the stable range (0.11 instead of 0.10 or less). On phones and slower connections, that wait can make the page feel unresponsive and cause people to leave before reading or contacting Yana. Improving the main-content delay should have the clearest visitor benefit; Core Web Vitals are also one of Google’s many page-experience signals.

Serious issue: Saved PageSpeed lab results

The table below summarizes Google PageSpeed Insights tests run on six pages in mobile and desktop modes. PageSpeed uses a controlled test to estimate how quickly a page loads and gives it a score from 0 to 100; 90 to 100 is the ideal range.

Every tested page currently has a lower mobile score. Mobile Largest Contentful Paint (LCP)—when the main content appears—ranges from 14.7 to 15.8 seconds, compared with the ideal 2.5 seconds or less. Mobile blocking time ranges from 130 to 380 milliseconds, compared with the ideal 200 milliseconds or less.

On smaller screens, scroll the table sideways to view every column.

PageMobile performanceDesktop performanceMobile Largest Contentful Paint (LCP)Mobile blocking time
Homepage537015.8 s210 ms
Partner institutions558814.8 s180 ms
Blog498315.3 s330 ms
Success stories568114.7 s130 ms
Learn about me508515.5 s320 ms
Learn about Germany488015.1 s380 ms

The tested pages currently score 92 on Lighthouse’s SEO checklist and 96 on Best Practices; accessibility ranges from 89 to 95. These scores show that many automated checks pass, but they do not measure rankings, content usefulness, search demand, backlinks, or lead quality. The lower performance results remain relevant because slow pages can affect visitors even when the SEO checklist is high.

Resources: PageSpeed summary, all six Google mobile and desktop report links, and direct document observations.

Related improvement plan: improve the slow mobile first view.

4

Needs improvement: Search & inquiry measurement access

Which business-performance data was and was not available for this review.

Good: Public-site audit data was available

The review used the live site, sitemap crawl, Ubersuggest, GTmetrix, PageSpeed reports, and browser observations. This is enough to describe the site’s public technical condition, but not its actual search or inquiry results.

Needs improvement: Private performance data was not supplied

The audit did not include access to Google Search Console, Google Analytics, or lead records. Google does not require these tools for ranking, but without them this report cannot identify which searches bring visitors or which pages produce inquiries. Reviewing that data could show which parts of the site already produce results and where improvement would matter most.

Resources: audit scope and data limitations and measurement inputs for a future account review.

Related improvement plan: measurement access and review.

Checkup sections