SEOking

Website audit report

avito.ma

66
/ 100
C · Needs work

1 critical and 6 high-severity issues found across 119 checks.

Checks run
119
Passed
65
Failed
43
Pages crawled
12

Scanned 2026-09-04T00:45:54+00:00 · 4 host IPs · cert expires in 121 days

This report is not offered to search engines. It is reachable by link only. If you own avito.ma you can publish or delete it.

How you compare

Measured against every site SEOking has audited: a corpus that grows with each scan and cannot be reconstructed after the fact.

Your position

32th percentile of 31 sites audited. The average site scores 72, the median 71.

The most unusual thing you fail

The mobile page matches the desktop page

92% of the sites we have audited get this right and yours does not. Of everything on this report, it is the fault that most sets you apart from your competition, which makes it the first thing worth fixing.

Inbox Trust Index

Our own measure of whether your domain is trusted by the systems that decide if mail reaches an inbox. No other website audit reports this. It is built from BounceZero's deliverability platform.

65
/ 100
Fair

Working, but with faults that measurably cost you inbox placement.

What is pulling it down: DMARC enforcement. See the email deliverability section below.

Measured against our corpus

We have measured deliverability across 237,421 domains. Yours is not among them, which simply means no one has needed to verify an address at it. The score above is from live measurements of your own DNS.

For context, 4.1% of the domains we have measured accept mail to any address, which makes their bounce behaviour unpredictable.

Your plan

The 43 faults on this report come from 18 underlying causes. Fixing a cause fixes everything under it, so this is ordered by score returned per unit of work, not by severity alone.

The 8 quickest steps here take you from 66 to about 76. That is 10 points for changes measured in minutes and hours, not weeks.

  1. 1. Stop JavaScript overriding the indexing directives

    Development work · days to weeks→ 68/100

    A canonical or noindex injected at runtime silently overrides what the server said, and the served HTML still looks correct to anyone reading the source.

    Fixes 2 findings: JavaScript does not rewrite indexing directives · The title survives rendering

  2. 2. Fix email authentication

    DNS edit · minutes→ 72/100

    These are all records in your DNS. One editing session fixes every one of them, and it is the change most likely to stop your mail being filtered.

    Fixes 5 findings: DMARC policy is enforced · DMARC reports are collected · MTA-STS policy published · TLS reporting enabled · BIMI logo published

  3. 3. Make the structured data qualify

    Template change · a few hours→ 78/100

    Rich results — ratings, prices, FAQs, breadcrumbs — are what turn a listing into an advert, and they are decided by whether a few required properties are present. Markup that is invalid or incomplete is work already done that currently earns nothing.

    Fixes 6 findings: The business is a describable entity · Content is marked up to be answered · The business is identified in structured data · Breadcrumbs are marked up · Site-wide search is declared · The entity links out to its profiles

  4. 4. Close the takeover and impersonation gaps

    DNS edit · minutes→ 79/100

    A subdomain pointing at a service that released it can be claimed by anyone, who then publishes on your domain. Deleting the record costs nothing and closes it immediately.

    Fixes 1 finding: No lookalike domain can send mail as your brand

  5. 5. Point the site's own authority at the pages that earn

    Template change · a few hours→ 82/100

    Internal links decide which of your pages search engines treat as important, and the decision is usually an accident of navigation design. It costs nothing to change and it changes what ranks.

    Fixes 3 findings: Every page is linked from another · Each page covers a distinct subject · Every page is linked from somewhere

  6. 6. Complete the security headers

    Server or CDN config · under an hour→ 83/100

    All set in the same place — your web server or CDN. Half of them are single lines.

    Fixes 4 findings: Content Security Policy header · MIME sniffing protection header · Clickjacking protection header · Referrer policy header

  7. 7. Write the titles and descriptions

    Content work · days→ 86/100

    Your title and description are the advert Google runs for you, free, every time someone searches.

    Fixes 4 findings: Meta descriptions are unique · Structured data present · Social preview configured · Link previews are configured for X/Twitter

  8. 8. Make the mobile page the equal of the desktop page

    Template change · a few hours→ 88/100

    Google indexes the mobile version. Anything missing from what a phone is served is missing from the index, however complete the desktop page is — and no desktop audit can see it.

    Fixes 1 finding: The mobile page matches the desktop page

  9. 9. Remaining individual fixes

    Mixed · varies→ 90/100

    These do not share a root cause with anything else on the report.

    Fixes 2 findings: Pages deliver what their titles promise · No phrase is repeated unnaturally

  10. 10. Correct caching and compression at the origin

    Server or CDN config · under an hour→ 91/100

    One misconfigured cache header suppresses browser caching, CDN caching and compression at once. Fixing it speeds up every page for every visitor, including the ones your ads paid for.

    Fixes 1 finding: Browser caching is allowed

  11. 11. Fix what search engines are allowed to see

    Server or CDN config · under an hour→ 92/100

    These decide whether your pages can appear at all. Nothing else on this report matters until they are right.

    Fixes 1 finding: Homepage canonical is correct

  12. 12. Reduce what the page has to load

    Development work · days to weeks→ 95/100

    Image and script weight drive every speed metric you are failing. This is the slowest fix here and the one with the longest tail.

    Fixes 3 findings: Reasonable number of scripts · Images declare width and height · Images load lazily

  13. 13. Harden DNS and hosting

    Server or CDN config · under an hour→ 95/100

    Resilience and reputation work — lower urgency, but cheap while you are already in these systems.

    Fixes 3 findings: Certificate surface is proportionate · DNSSEC enabled · CAA record restricts certificate issuance

  14. 14. Fix the page on a phone

    Template change · a few hours→ 96/100

    Google indexes the mobile version of your site, and these are measured in a real phone-sized browser rather than inferred. A page that scrolls sideways or needs pinching to read loses the visitor before the content matters.

    Fixes 1 finding: Tap targets are big enough to hit

  15. 15. Tidy the URL structure

    Server or CDN config · under an hour→ 97/100

    Depth decides how much authority reaches a page and how often it is recrawled; parameters and capitals manufacture duplicate URLs that compete with the originals.

    Fixes 1 finding: URLs are readable

  16. 16. Show who stands behind the content

    Content work · days→ 98/100

    Google's guidance asks who produced a page and why they should be trusted. For advice, health, legal or financial topics an anonymous, undated page competes badly against a named one.

    Fixes 2 findings: There is a route to who you are · A publisher is declared in structured data

  17. 17. Serve images at the right size and format

    Development work · days to weeks→ 100/100

    Images are what Largest Contentful Paint usually measures, and WebP is typically a third smaller than the same JPEG. On image-led pages this is the largest saving available.

    Fixes 2 findings: Images use a modern format · Images are sized for the device

  18. 18. Decide whether AI assistants may cite you

    Server or CDN config · under an hour→ 100/100

    A growing share of questions are answered without a results page. Being quotable is a distribution channel, and it is usually blocked by a plugin default rather than a decision.

    Fixes 1 finding: A curated summary is published for assistants

Fix these first

Ranked by severity, then by how much score each returns.

  1. high

    1. The mobile page matches the desktop page

    +10 pts

    The server sends a phone something different: the mobile page carries 157 words against 234 on desktop. Google indexes the mobile version of your site, so whatever is missing there is missing from the index — regardless of how complete the desktop page is. This is invisible to any check performed from a desktop user agent, which is most of them.

    desktop: 234 words, 60 internal links
    mobile:  157 words, 61 internal links

    How to fix: Serve the same content, links and meta tags to every device. If you use separate mobile templates or dynamic serving, the mobile one is the version that matters.

  2. critical

    2. JavaScript does not rewrite indexing directives

    +9 pts

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    robots: served 'index, follow', rendered 'noindex,nofollow'

    How to fix: Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  3. high

    3. DMARC policy is enforced

    +9 pts

    DMARC policy is p=none. p=none monitors only — it instructs receivers to do nothing, so nobody is actually prevented from spoofing your domain.

    v=DMARC1; p=none;

    How to fix: Move to p=quarantine, then p=reject, once your reports are clean.

  4. high

    4. No lookalike domain can send mail as your brand

    +8 pts

    We generated and checked 47 plausible misspellings and variants of your domain. 8 of the 10 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    avito.co   [mail configured]
    avito.com   [mail configured]
    avito.info   [mail configured]
    avito.io   [mail configured]
    avito.online   [mail configured]
    avito.org   [mail configured]
    avito.site   [mail configured]
    vito.ma   [mail configured]

    How to fix: Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  5. high

    5. Browser caching is allowed

    +6 pts

    This site tells browsers never to store anything. Every returning visitor re-downloads the entire page. This belongs on cart and checkout pages only.

    cache-control: private, no-cache, no-store, max-age=0, must-revalidate

    How to fix: Restrict no-store to authenticated pages and let everything else cache.

Full results

Security & trust

Whether the connection, certificate and headers hold up.

7 passed · 4 failed
83%
  • Content Security Policy headermedium

    Missing. Limits where scripts may load from, which is the main defence against injected code and card skimmers.

    Add a Content-Security-Policy header, starting in report-only mode.

  • MIME sniffing protection headerlow

    Missing. Stops browsers guessing file types.

    Send X-Content-Type-Options: nosniff

  • Clickjacking protection headerlow

    Missing. Stops your site being framed inside someone else's.

    Send X-Frame-Options: SAMEORIGIN, or use CSP frame-ancestors.

  • Referrer policy headerlow

    Missing. Controls how much of your URL is leaked to other sites.

    Send Referrer-Policy: strict-origin-when-cross-origin

  • Served over HTTPS

    Secure connection working.

  • HTTP redirects to HTTPS

    Plain HTTP requests are redirected to the secure version.

  • No insecure mixed content

    All resources load securely.

  • Cookies are protected

    Cookies set Secure and HttpOnly.

  • Certificate is not near expiry

    Certificate valid for another 121 days (expires 2027-01-03).

  • Modern TLS version

    Negotiated TLSv1.3.

  • HSTS header

    HSTS is set.

Email deliverability

Whether your mail reaches inboxes or spam folders.

5 passed · 5 failed
69%
  • DMARC policy is enforcedhigh

    DMARC policy is p=none. p=none monitors only — it instructs receivers to do nothing, so nobody is actually prevented from spoofing your domain.

    v=DMARC1; p=none;

    Move to p=quarantine, then p=reject, once your reports are clean.

  • DMARC reports are collectedmedium

    No rua= address, so DMARC failures are generated and then discarded. You have no visibility into who is sending as you.

    v=DMARC1; p=none;

    Add rua=mailto:dmarc@yourdomain to start collecting reports.

  • MTA-STS policy publishedlow

    No MTA-STS policy, so mail to you can be delivered unencrypted if an attacker strips TLS.

    Publish an MTA-STS policy and the _mta-sts TXT record.

  • TLS reporting enabledlow

    No TLS-RPT record, so delivery-encryption failures go unreported.

    Publish a _smtp._tls TXT record with a reporting address.

  • BIMI logo publishedlow

    No BIMI record. With DMARC at enforcement you could display your logo next to your messages in Gmail and Apple Mail.

    Once DMARC is at quarantine or reject, publish a BIMI record with an SVG logo.

  • DKIM signing is configured

    DKIM keys published on selector(s): google, k1, s1, s2, mandrill.

  • Domain can receive email

    5 mail server(s) configured.

  • SPF ends with a fail qualifier

    Ends in ~all (soft fail) — the usual safe setting.

  • SPF stays under the lookup limit

    The record forces about 6 DNS lookups. Comfortably within the limit of 10.

  • Exactly one SPF record

    One SPF record, as required.

Speed & Core Web Vitals

How fast real visitors experience the site.

3 passed · 6 failed · 1 skipped
39%
  • Browser caching is allowedhigh

    This site tells browsers never to store anything. Every returning visitor re-downloads the entire page. This belongs on cart and checkout pages only.

    cache-control: private, no-cache, no-store, max-age=0, must-revalidate

    Restrict no-store to authenticated pages and let everything else cache.

  • Images declare width and heightmedium

    0 of 27 images declare dimensions. Images without dimensions cause the page to jump as they load, which is what Cumulative Layout Shift measures.

    Set width and height attributes on every image.

  • Images use a modern formatmedium

    All 59 image(s) are JPEG or PNG, with no WebP or AVIF alternative. WebP is typically 25-35% smaller at the same quality and is supported by every current browser — on image-led pages this is usually the single largest saving available, and images are what Largest Contentful Paint measures.

    https://assets.avito.ma/icons/png/pop-cat-2030-sell.png, https://assets.avito.ma/icons/png/pop-cat-1010-let.png, https://assets.avito.ma/icons/png/pop-cat-3000-sell.png, https://assets.avito.ma/icons/png/pop-cat-5000-sell.png

    Serve WebP or AVIF with a <picture> element falling back to the original, or enable automatic conversion at your CDN.

  • Reasonable number of scriptsmedium

    28 external script file(s) on the homepage. Each one is a separate request that can block rendering.

    Remove unused third-party tags and combine what remains.

  • Images load lazilylow

    4 of 27 images use lazy loading.

    Add loading="lazy" to images below the fold.

  • Images are sized for the devicelow

    129 of 539 image(s) provide a srcset. Without one, a phone downloads the full desktop image and then scales it down — paying for pixels it never shows.

    Add srcset and sizes so each device downloads an appropriate image.

  • Core Web Vitals from real users

    Not available: PageSpeed API returned 429. This usually means the site does not yet have enough Chrome traffic for Google to report field data. Lab measurements below still apply.

  • Compression enabled

    Served with gzip compression.

  • Server responds quickly

    Median response across 12 page(s) was 544 ms.

  • Homepage HTML is not oversized

    Homepage HTML is 246 KB.

Search fundamentals

The tags, files and signals search engines read first.

18 passed · 12 failed · 3 skipped
71%
  • The business is a describable entityhigh

    No Organization or Person markup. An assistant that cannot name the entity behind the site will describe the business from fragments, or not at all, which is how a competitor becomes the answer.

    Add Organization JSON-LD with name, url, logo and sameAs links, so the description an assistant gives of the business is the one you wrote.

  • Content is marked up to be answeredhigh

    No FAQPage, HowTo or QAPage markup. When an assistant answers a question about this service, the page has nothing structured to be cited from, so the citation goes to whoever wrote the answer block.

    Add FAQPage schema for the questions the page answers (the answer must appear as visible text, not only in the markup) and HowTo for process content.

  • The business is identified in structured datamedium

    No Organization markup. This is what Google assembles a knowledge panel from — the box with your logo, name and links that appears beside branded searches — and what connects your site to your social profiles. Without it Google infers your identity from third parties instead of from you.

    Add Organization JSON-LD with name, url, logo and sameAs links to your social profiles.

  • Homepage canonical is correctmedium

    No canonical tag, so duplicate URLs of the same page can compete.

    Set a self-referencing canonical on every page.

  • Structured data presentmedium

    No structured data. Google is reading your page as plain text and cannot qualify you for any rich result.

    Add JSON-LD for Organization and your primary content type.

  • Breadcrumbs are marked upmedium

    No BreadcrumbList markup. Google replaces the raw URL in your listing with a readable breadcrumb trail when this is present, which is more legible and measurably more clickable — and it is one of the cheapest rich results to earn.

    Add BreadcrumbList JSON-LD to every page below the homepage.

  • The entity links out to its profileslow

    No entity markup to attach profiles to.

    Add sameAs URLs to the Google Business Profile, LinkedIn, X and any other profiles the business owns.

  • Social preview configuredlow

    No Open Graph tags, so links shared on social or WhatsApp show no image, title or description.

    Add og:title, og:description and og:image.

  • URLs are readablelow

    5 URL(s) contain capitals, spaces, underscores or a file extension. Google treats /Page and /page as different URLs, so capitals invite duplicates, and underscores are not read as word separators the way hyphens are.

    https://www.avito.ma/fr/boutiques/maroc/%C3%A0_vendre
    https://www.avito.ma/fr/al_hoceima
    https://www.avito.ma/fr/boutiques/maroc/immobilier-%C3%A0_vendre
    https://www.avito.ma/fr/beni_mellal
    https://www.avito.ma/fr/el_jadida
    5 affected URLs

    Use lowercase words separated by hyphens, with no file extension. Redirect the old URLs to the new ones.

  • Site-wide search is declaredlow

    No WebSite markup. With a SearchAction it can give you a search box directly inside your Google listing for branded queries.

    Add WebSite JSON-LD, with potentialAction/SearchAction if the site has its own search.

  • Link previews are configured for X/Twitterlow

    No twitter:card tags. Open Graph covers most platforms, but X falls back to a bare link without them, and a link with no image or title is measurably less likely to be opened.

    Add twitter:card ("summary_large_image"), twitter:title and twitter:description.

  • A curated summary is published for assistantslow

    No /llms.txt. It is a short, plain-text map of what a site is and which pages matter — a convention some assistants read to decide what to quote, and cheap to publish. It is not yet a standard anyone is obliged to honour, so treat it as a low-cost bet rather than a requirement.

    Publish /llms.txt: a heading, one paragraph describing the business, and a linked list of your most important pages.

  • International targeting

    Not applicable — this site publishes in a single language and declares no regional or translated versions, so hreflang annotations are not needed. Adding them to a single-language site does nothing.

  • Search Console connected

    Not measured — not configured on this instance. Connecting Search Console adds what no crawl can see: the queries this site already appears for, where it ranks, and how many people click. It is read-only and can be disconnected at any time.

  • Current search visibility

    Not measured — ranking data is not configured on this instance.

  • Homepage is indexable

    Homepage is open to indexing.

  • Mobile viewport declared

    Mobile viewport is declared.

  • Homepage title is present and well sized

    Title is 28 characters.

  • XML sitemap published

    Sitemap found listing 0 URLs.

  • Homepage meta description is present

    Description is 152 characters.

  • robots.txt does not block the site

    robots.txt present and open to search engines.

  • Canonicals point at indexable pages

    Every canonical points at a page that is allowed to be indexed.

  • Canonical targets are live pages

    Canonical targets all return 200.

  • Structured data parses

    All structured data blocks are valid JSON.

  • Noindex directives are readable

    No page relies on a directive Google is blocked from reading.

  • Marked-up content qualifies for rich results

    Every marked-up entity carries the properties Google requires.

  • Most crawled pages are indexable

    10 of 12 crawled page(s) (83%) can actually be indexed.

  • No canonical chains

    No canonical points at a page that then canonicals somewhere else.

  • AI assistants can cite this site

    Every major assistant is allowed to read and cite these pages.

  • Pages are close to the homepage

    Every crawled page sits within four levels of the homepage (deepest: 4).

  • Content is not served behind query parameters

    0 of 12 crawled URLs carry query parameters other than tracking tags.

  • Page language declared

    Language attribute present.

  • Model-training access is stated

    No model-training crawler is blocked, so this content may be used to train future models. This is a business decision rather than an SEO one, and it is separate from being cited in answers: refusing training does not remove you from AI results, and allowing it does not put you in them.

Content & structure

Whether pages are unique, linked and crawlable.

19 passed · 8 failed · 1 skipped
67%
  • Every page is linked from somewheremedium

    1 of 12 crawled pages had no internal link pointing at them. Search engines discover pages by following links, so an unlinked page is found late or not at all — and passes on none of its authority.

    1 affected URL

    Link these from a relevant parent page, your navigation, or a hub page.

  • Each page covers a distinct subjectmedium

    37 pair(s) of pages appear to cover the same subject, judged from their titles and headings. Two pages competing for one query split the links and relevance that should accumulate on one, and Google alternates between them — so neither settles into a stable position. Confirm against Search Console, which shows exactly which page it chooses.

    Boutiques dans Tout le Maroc | Avito.ma
       https://www.avito.ma/fr/boutiques/maroc/%C3%A0_vendre
       https://www.avito.ma/fr/boutiques/maroc/immobilier-%C3%A0_vendre
    Achetez et vendez en ligne près de chez vous à Al Hoceima Ma
       https://www.avito.ma/fr/al_hoceima
       https://www.avito.ma/fr/fes
    Achetez et vendez en ligne près de chez vous à Béni Mellal M
       https://www.avito.ma/fr/beni_mellal
       https://www.avito.ma/fr/fes
    Achetez et vendez en ligne près de chez vous à Agadir Maroc 
       https://www.avito.ma/fr/agadir
       https://www.avito.ma/fr/fes
    10 affected URLs

    Decide which page owns the subject. Merge the weaker one into it and redirect, or narrow each to a genuinely different question.

  • Pages deliver what their titles promisemedium

    9 page(s) have a title and heading whose subject barely appears in the body. Either the title is written for a query the page does not answer — which loses the visitor on arrival and is measurable as a bounce — or the page is about something its title does not say.

    17% of the title's subject in the body
       Achetez et vendez en ligne près de chez vous à Al Hoceima Ma
       https://www.avito.ma/fr/al_hoceima
    17% of the title's subject in the body
       Achetez et vendez en ligne près de chez vous à Béni Mellal M
       https://www.avito.ma/fr/beni_mellal
    33% of the title's subject in the body
       Achetez et vendez en ligne près de chez vous à Agadir Maroc 
       https://www.avito.ma/fr/agadir
    25% of the title's subject in the body
       Achetez et vendez en ligne près de chez vous à El Jadida Mar
       https://www.avito.ma/fr/el_jadida
    9 affected URLs

    Make the opening paragraph answer the title directly, or change the title to what the page is really about.

  • Meta descriptions are uniquemedium

    9 pages share 1 duplicated meta description(s). A description is the advert for that specific page; repeating one across a site means Google usually discards it and writes its own from the page text, so you lose control of what searchers read before deciding whether to click.

    Avito ✅ la première plateforme de vente et d&#x27;achat en ligne au Maroc…
       used on 9 pages
    9 affected URLs

    Write one description per page, describing what is on that page.

  • Every page is linked from anothermedium

    1 crawled page(s) are not linked from any other page we fetched. A page reachable only from a sitemap receives no internal authority at all, and is crawled rarely — it can rank, but it starts from nothing and stays there.

    avito.ma/fr/boutiques/maroc/%C3%A0_vendre
    1 affected URL

    Link them from a relevant hub page or from navigation, using the subject as the link text.

  • No phrase is repeated unnaturallymedium

    17 phrase(s) make up more than 5% of a page's own words. Repetition at that level reads badly to a person and has not helped rankings in over a decade — it is now a signal in the wrong direction.

    "membre depuis" is 19% of the page
       https://www.avito.ma/fr/boutiques/maroc/%C3%A0_vendre
    "al hoceima" is 23% of the page
       https://www.avito.ma/fr/al_hoceima
    "hoceima il" is 18% of the page
       https://www.avito.ma/fr/al_hoceima
    "il heures" is 18% of the page
       https://www.avito.ma/fr/al_hoceima
    "membre depuis" is 20% of the page
       https://www.avito.ma/fr/boutiques/maroc/immobilier-%C3%A0_vendre
    10 affected URLs

    Write the phrase once where it belongs and use natural variations elsewhere.

  • There is a route to who you aremedium

    No link to an about, team or contact page was found in the pages crawled. These are the pages both people and search engines use to decide whether a site belongs to a real business, and their absence is one of the strongest signals of a site that is not worth trusting.

    Link an About and a Contact page from your main navigation or footer.

  • A publisher is declared in structured datalow

    No publisher in your structured data. It ties each page back to the organisation that stands behind it, which is what carries trust from your brand to an individual article.

    Add a publisher property naming your Organization, with its logo.

  • Content carries recent dates

    Not measured — no page declares a publication or modification date, so how recently the site was maintained cannot be determined. That is normal for a brochure site and worth fixing for anything article-based.

  • Page titles are unique

    All 12 crawled pages have distinct titles.

  • Pages carry more than their template

    Across 12 page(s), the median page is 48% its own content and the rest navigation, footer and legal text.

    1 affected URL
  • Pages have enough content

    All 12 crawled pages carry substantial content.

  • Every page has a meta description

    0 of 12 crawled pages have no meta description.

  • Images have alt text

    0 of 539 images across the crawl have no alt attribute. Alt text is how search engines read images and how screen readers describe them.

  • Navigation is present on every page

    Every crawled page carries at least three internal links, so navigation is consistently rendered.

  • Pages are meaningfully different from each other

    No two crawled pages share substantially the same text.

  • No broken internal pages

    All 12 crawled pages returned successfully.

  • Missing pages return a real 404

    No page answers 200 while telling the visitor nothing was found.

  • Navigation promotes pages that earn money

    134 link(s) appear on nearly every page — the site-wide navigation, which is where most internal authority is allocated.

  • Content identifies who wrote it

    Authorship is declared.

  • Links describe where they go

    71 of 2196 internal link(s) use text like 'click here' or no text at all.

  • The writing is readable

    Median reading ease is 50.3 — fairly hard.

  • One H1 per page

    1 of 12 pages do not have exactly one H1 heading.

    1 affected URL
  • No long redirect chains

    No multi-step redirects found.

  • No dead-end pages

    Every crawled page links onward.

  • Internal authority is spread, not pooled

    Pages receive 8.4 internal links on average across the crawl, with no single page absorbing most of them.

  • Where internal authority goes

    Internal links concentrate authority on the pages below, in order. This is the site's own ranking of itself, derived from how it links — read it against what the business actually sells, because search engines read it the same way. Only the crawled sample is modelled, so this describes the navigation rather than every page.

  • What each page is about

    The terms that distinguish each page from the others on this site — not the most frequent words, but the ones this page uses and the others do not. Read them as what a search engine would take the page to be about, and check that it matches what it is for.

Local business signals

What Google needs to place you in map results.

0 passed · 0 failed · 1 skipped
100%
  • Local business signals

    Not applicable — nothing on this site indicates a physical location customers visit: no address, phone link, opening hours, map or local business markup. Local search checks are skipped and do not affect the score. If you do serve customers from premises, publishing an address and phone number is the place to start.

Infrastructure

DNS, hosting and delivery configuration.

11 passed · 4 failed · 3 skipped
79%
  • No lookalike domain can send mail as your brandhigh

    We generated and checked 47 plausible misspellings and variants of your domain. 8 of the 10 registered variants has mail servers configured, so it is technically able to send email that reads as yours to anyone skimming a sender address. Many such domains are entirely unrelated businesses that happen to have a similar name — this is a risk to be aware of and to defend against, not evidence that anyone is doing anything.

    avito.co   [mail configured]
    avito.com   [mail configured]
    avito.info   [mail configured]
    avito.io   [mail configured]
    avito.online   [mail configured]
    avito.org   [mail configured]
    avito.site   [mail configured]
    vito.ma   [mail configured]

    Publish DMARC at enforcement so mail claiming to be your domain is rejected outright — that is the defence that works regardless of who owns a lookalike. Then register the closest unregistered variants; they cost a few pounds a year and are the cheapest brand protection available.

  • Certificate surface is proportionatemedium

    345 hostname(s) appear in this domain's public certificate history, issued by Let's Encrypt, Amazon. A large certified surface is a large attack surface, and every one of those names is public — certificate transparency is a permanent, searchable log.

    Retire certificates for hosts you no longer run, and prefer wildcard certificates where you genuinely need many subdomains.

  • DNSSEC enabledlow

    DNSSEC is not enabled, so DNS answers for your domain can't be cryptographically verified.

    Enable DNSSEC at your DNS provider.

  • CAA record restricts certificate issuancelow

    No CAA record, so any certificate authority may issue certificates for your domain.

    Publish a CAA record naming the certificate authority you use.

  • Mail server IP is not blacklisted

    Not checked: the blocklists declined queries from this resolver, so reputation could not be confirmed either way. This is excluded from your score rather than guessed at.

  • Server log analysis

    Not measured — no log file supplied. Server logs are the only source that shows what Googlebot actually fetched rather than what it could fetch: which pages it spends its crawl on, which it has never asked for, and what it receives when it does.

  • Whole-site analysis

    Not measured — no whole-site crawl has been run for this domain. The audit above reasons from a sample of pages chosen to cover each template, which describes how the site is built. It cannot say how many of the site's pages are indexable, which templates are thin across every instance, or what sits too deep to be crawled — those are counts, and a sample cannot produce one.

  • Redundant nameservers

    2 nameserver(s) configured.

  • No subdomain can be taken over

    Checked 25 subdomain(s); none point at a cloud service that has released them.

  • No staging or development sites are publicly indexable

    Certificate transparency lists 345 hostname(s) for this domain and none of the development-style hosts are both live and open to indexing.

  • No unbounded URL spaces

    No filter, session or calendar URLs that would generate an unbounded space were found.

  • Pages are reached without redirect chains

    Every page was reached directly or in a single hop.

  • Crawled URLs return content

    0 of 12 URL(s) followed during this crawl returned a redirect or an error (0%).

  • Certificate is not shared with unrelated domains

    Your certificate covers only your own domain.

  • Internal links pass authority

    0 internal link(s) are marked nofollow.

  • Software versions are not disclosed

    No version numbers advertised in response headers.

  • Hosting network identified

    Served from AS13335 (CLOUDFLARENET - Cloudflare, Inc.), announced in 104.20.0.0/20 — a block of 4,096 addresses.

  • What this audit examined

    12 page(s) were examined, chosen to cover 11 of the 40 distinct page templates found across 12 known URLs. Pages are sampled by template rather than in sitemap order, because the first pages of a sitemap are usually all the same kind — a sample of one template would describe that template rather than the site. Findings below therefore apply to the templates listed, and a fault in a template is normally a fault on every page built from it.

Off-page authority

Who links to this site, with what text, and how that compares.

0 passed · 0 failed · 1 skipped
100%
  • Off-page profile

    Not measured — off-page data is not configured on this instance.

What Google's renderer sees

The site loaded in a real browser, the way a visitor and a crawler get it.

2 passed · 4 failed · 1 skipped
24%
  • JavaScript does not rewrite indexing directivescritical

    JavaScript changes the directives Google acts on after the page loads. The served HTML looks correct to anyone reading the source, and Google indexes what rendering produced — so a canonical or noindex injected at runtime silently overrides everything the server said.

    robots: served 'index, follow', rendered 'noindex,nofollow'

    Emit the final canonical and robots directives server-side. Nothing that decides indexing should depend on a script running.

  • The mobile page matches the desktop pagehigh

    The server sends a phone something different: the mobile page carries 157 words against 234 on desktop. Google indexes the mobile version of your site, so whatever is missing there is missing from the index — regardless of how complete the desktop page is. This is invisible to any check performed from a desktop user agent, which is most of them.

    desktop: 234 words, 60 internal links
    mobile:  157 words, 61 internal links

    Serve the same content, links and meta tags to every device. If you use separate mobile templates or dynamic serving, the mobile one is the version that matters.

  • Tap targets are big enough to hitmedium

    2 of 2 tappable element(s) are smaller than 48x48 pixels. On a phone that means links and buttons that are hard to hit without zooming, and mis-taps on a checkout or contact button cost conversions directly.

    Cloudflare (57x18)
    Privacy (40x18)

    Give tappable elements at least 48x48 CSS pixels and 8 pixels of spacing — usually padding on the link rather than a bigger font.

  • The title survives renderingmedium

    The title tag changes after JavaScript runs. Google usually indexes the rendered title, but rendering is queued separately and can lag the first crawl, so for a while the served title is what appears in results.

    served:   Annonces au Maroc | Avito.ma
    rendered: Just a moment...

    Render the final title server-side.

  • Rendered-page analysis

    Not measured: the browser pass did not run. Everything else in this report is unaffected — these checks are excluded from your score rather than guessed at.

  • The page fits the screen

    The page fits the mobile viewport with no sideways scrolling.

  • Body text is legible on a phone

    0 of 7 text block(s) render below 12px on a mobile viewport.

Scan details

Final URLhttps://www.avito.ma/
Host IPs104.20.10.134, 104.20.9.134, 2606:4700:10::6814:986, 2606:4700:10::6814:a86
Pages crawled12 of 12 attempted
Sitemap URLs0
Nameserversfiona.ns.cloudflare.com, jobs.ns.cloudflare.com
Mail serversalt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx.l.google.com
DKIM selectorsgoogle, k1, s1, s2, mandrill
Mail server IPs172.253.157.26, 142.250.102.27, 192.178.213.26
TLSTLSv1.3 · TLS_AES_256_GCM_SHA384 · issued by Sectigo Limited
Detected stackNext.js / Cloudflare / Cloudflare · mail on Google Workspace
12 URLs crawled
  • https://www.avito.ma/
  • https://www.avito.ma/fr/boutiques/maroc/%C3%A0_vendre
  • https://www.avito.ma/fr/al_hoceima
  • https://www.avito.ma/fr/boutiques/maroc/immobilier-%C3%A0_vendre
  • https://www.avito.ma/fr/beni_mellal
  • https://www.avito.ma/fr/agadir
  • https://www.avito.ma/fr/el_jadida
  • https://www.avito.ma/fr/casablanca
  • https://www.avito.ma/fr/errachidia
  • https://www.avito.ma/fr/kenitra
  • https://www.avito.ma/fr/fes
  • https://www.avito.ma/fr/khenifra

Want these fixed?

BounceZero Ltd does this work: technical remediation, local SEO and email deliverability. Tell us what you want fixed and we'll reply with what it takes. No call required, no obligation.

We only email you about this request. No list, no newsletter.

Watch this site

We re-audit on a schedule and email you only when a check that was passing starts failing. That is usually a recent change to the site or its DNS, and it is findable while still fresh. No digest, no newsletter.

Monitoring means repeatedly fetching your site and emailing about it, so we ask you to prove you own avito.ma first.