Short answer: Two findings in the SEO area of a Site AI Audit report are about tags in the head of your page. “Pages are not set up for mobile screens” is a warning: the viewport tag is missing, so phones show a zoomed-out desktop page. “The page language is not declared” is a notice: the html tag has no lang attribute. Both fixes are one short line of HTML, and both are quick to verify with another check.
The two findings in plain words
Most findings in an audit need a bit of detective work. These two do not. They are about declarations that every modern page should make in its code, one about how to scale the page to the screen and one about the language of the text. When they are missing, nothing breaks in an obvious way on your desktop computer, which is why they are often forgotten. Visitors on phones and visitors who use assistive technology notice them first.
The report words them like this. The first finding says that without a viewport tag the page shows zoomed out on phones, and Google ranks by mobile experience. The advice is to add the viewport meta tag. The second says that search engines and screen readers use the lang attribute to serve the right audience, and the advice is to add lang=”en”, or your own language, to the html tag.
The viewport tag
The viewport meta tag tells a mobile browser how wide the page should be and how to scale it. Without it, a phone assumes that the page was designed for a wide desktop screen. It renders the page at a width of about 980 pixels and shrinks everything to fit. The result is tiny text, buttons too small to press and a lot of pinching and zooming. Even a page with a responsive design, one that adapts to narrow screens, needs this tag, because the browser has to be told to use the real screen width.
The standard line goes into the head of every page:
<meta name="viewport" content="width=device-width, initial-scale=1">
It says: use the width of the device, and start at a normal zoom level. The audit looks for this tag on every page it reads. If some pages lack it, they appear in the finding list. Because the finding is a warning, the cost to the SEO score is real: points are subtracted once for the finding, whatever the number of pages. The article on the viewport meta tag and mobile usability goes into details.
Why mobile setup matters for ranking
Google indexes the mobile version of pages first. That is explained in the guide to mobile-first indexing. A page that is hard to use on a phone gives a worse experience to most visitors, and search engines take that into account. More importantly, a visitor who has to zoom in to read leaves, and a lost visitor is lost whatever the ranking. For shops and booking sites the loss is direct. The viewport tag does not make a site responsive by itself, but without it nothing else about your mobile design can work.
What to avoid in the viewport tag
- Do not block zooming. Settings such as user-scalable=no or a very low maximum-scale take away a tool that people with low vision rely on.
- Do not fix the width to a number. A line such as width=1024 forces a desktop layout on a phone.
- Do not add the tag twice. Themes and plugins sometimes both print it. One is enough.
The language attribute
The lang attribute sits on the html tag and declares the language of the page, for example lang=”en” for English or lang=”lt” for Lithuanian. Regional variants are allowed, such as en-GB. The line looks like this:
<html lang="en">
It is used by:
- Screen readers, which choose the right voice and pronunciation. Without it, a page in German may be read aloud with English rules.
- Browsers, for hyphenation, quote marks, spell checking and the offer to translate the page.
- Search engines, which use it as one hint to show the page to people who speak that language.
The audit raises the notice only when none of the pages it read declare a language. If the declaration is missing on every page, it is almost always a theme setting or a template, and one change fixes the whole site. The guide to the HTML lang attribute has more on this, and the article on hreflang explains how language versions of a page are linked to each other, which is a separate topic.
How to add the tags
WordPress
Almost every current theme prints both tags. If yours does not, the theme file header.php normally contains the head and the html tag. The language comes from the site language setting in the general settings, and the theme prints it with the language attributes function. A missing viewport usually points to an outdated theme or to a custom theme where the line was never added. Add it in a child theme, so that updates do not remove it. The article on Site AI Audit for WordPress owners explains how to work with the report on a WordPress site.
Website builders and shop platforms
Most builders set both tags for you. If the report says they are missing, look for custom code in the header, for an old template or for a language setting that has not been filled in.
Hand-coded sites
Open the template or the layout file and make sure that the html tag has lang and that the head contains the viewport line. If your pages are generated from several templates, check each one.
Multilingual sites
If your site has several languages, each page should declare its own. The English pages carry lang=”en”, the Lithuanian ones lang=”lt” and so on. A wrong declaration is worse than none at all: a Lithuanian page marked as English will be read with English pronunciation. Language plugins normally take care of this, but check a page in each language. The audit looks at whether the declaration is present, not whether it is correct, so a manual check of the value is up to you.
How to check your fix
- View the page source and look at the start of the document: the html tag with lang, and the head with the viewport line.
- Open the page on a phone, or use the device mode in your browser’s developer tools. Text should be readable without zooming.
- Test one page in Site AI Audit by entering its full address, as described in the article on single-page checks.
- Run a full audit to confirm that every page is covered, and that the findings are gone.
A two-minute template check
You do not need an audit to see whether these tags are present, although the audit is the quickest way to check all pages at once. Open any page of your site, right-click and choose “view page source”, then read the first lines. The very first tag should be the html tag, and it should contain lang with a value. Within the first screen of the head, you should see a meta line with the name viewport. If either is missing in one page, look at whether other page types, such as the home page, a blog post and a product page, use different templates. A site often has three or four templates, and the fix may need to be made in each of them.
It is also worth testing the result with a real phone, or at least with the device mode of your browser, and with a page in each language. A tag in the code is only a promise; what matters is that the page then looks and reads properly.
A worked example
A family-run cabin rental has a site built ten years ago by a freelancer. The audit reports a warning, “Pages are not set up for mobile screens”, for all 24 pages, and a notice, “The page language is not declared”. The owner has never opened the site on a phone and is surprised to see tiny text. The new designer finds that the main template has no viewport tag and no lang attribute. She adds both lines to the one template. Because the layout already used fluid widths, the site now looks right on phones. A new audit shows both findings gone, and booking enquiries from phones start to rise within weeks.
To check your own pages, run a Site AI Audit with a free account. The plans unlock the full report with the list of affected pages.
Related reading
- Tap Targets and Font Size: Make Pages Easy to Use on Phones
- Accessibility and SEO: Where Fixing One Helps the Other
- H1 Heading Findings: Missing or Multiple Main Headings Explained
- Mobile Speed Findings in Site AI Audit: LCP, CLS and INP
The bottom line
Put the viewport tag in the head of every page and a lang attribute on the html tag. These two lines make pages readable on phones and understandable for screen readers and search engines. Run the audit again to see both findings disappear.
FAQ
Is the viewport tag still needed for a responsive site?
Yes. Without it, phones ignore your responsive layout and show a zoomed-out desktop version.
Why is the viewport finding a warning and the language one a notice?
The missing viewport damages the experience of most visitors, who are on phones. The missing language is a smaller problem, mostly for assistive technology and for hints to search engines.
Which value should lang have?
The code of the main language of the page, such as en, de or lt. A region can be added, such as en-GB.
Does the audit check that the language is correct?
No. It checks that the declaration exists. You need to make sure that the value matches the text on the page.
Can one template fix everything?
Usually yes. Both tags live in the shared head and html tag of the layout, so fixing the template fixes all pages that use it.



