Loading the report…
Loading the report…
An independent audit of duckdns.org, measured by Adnave on November 12, 2026. We read 12 pages of the site as a search engine first receives them and ran 43 checks. Organic health is 64 out of 100. The site lets the main AI assistants read it.
Growth Navigator · duckdns.org
23 opportunities to improve
12 pages read in full, 13 more links checked
Organic health
out of 100
Ads readiness
out of 100
Our suggested order: biggest obstacles first, quickest first among equals. The effect of each fix is not measured. 3 take minutes.
Step 1 · Organic
Everything here was observed on the site. Fixing it removes a known obstacle; no one can promise a specific ranking in return.
Observed · AdnaveBot's reading of 12 pages on 2026-11-12 · each finding is what we saw on those pages; “what to do”, the score and the order are our judgment
Only 34 words arrive with the page; the rest is built in the browser by scripts. Search engines may see very little.
What to do: Have the site send its main text in the page itself (server-side rendering or pre-rendering).
How to fix this: Thin content: what it is and how to fix itWhen someone shares the page, the preview will look bare or use the wrong image.
What to do: Add Open Graph tags: og:title, og:description and an og:image of 1200 × 630 pixels.
Paste inside the <head> of the page. Replace the image address with a picture of 1200 by 630 pixels.
<meta property="og:type" content="website"> <meta property="og:title" content="Duck DNS"> <meta property="og:description" content="Duck DNS free dynamic DNS hosted on Amazon VPC"> <meta property="og:url" content="https://www.duckdns.org/"> <meta property="og:image" content="https://www.duckdns.org/your-preview-image.png"> <meta name="twitter:card" content="summary_large_image">
The http:// version of the site still answers on its own, so some visitors and links stay on an insecure copy.
What to do: Redirect every http:// address to its https:// equivalent with a permanent (301) redirect.
For an Apache server, add to the top of the .htaccess file. Many hosts also offer this as a switch called “Force HTTPS”.
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]There is no structured data, so an assistant has to guess what the business is from loose text.
What to do: Add schema.org markup for the organisation, plus the type that fits the page: Product, Service, Article, FAQPage or SoftwareApplication.
Paste inside the <head> of the page. Fill in the name and logo address.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "duckdns.org",
"url": "https://www.duckdns.org",
"logo": "https://www.duckdns.org/your-logo.png"
}
</script>Pages under about 200 words rarely rank for anything.
What to do: Expand these pages with useful detail, merge them into a stronger page, or hide them from search.
“Duck DNS”. Titles outside roughly 30 to 60 characters are either vague or get cut off in results.
What to do: Rewrite it to 30 to 60 characters, leading with the main thing people search for.
How to fix this: How to write page titles and meta descriptionsA “noindex” instruction keeps these pages out of Google. That is right for things like a cart or login page, and a problem for pages you want found.
What to do: Review the list and remove noindex from any page that should appear in search.
“Duck DNS free dynamic DNS hosted on Amazon VPC”
What to do: Aim for 70 to 160 characters so it is specific but not cut off.
How to fix this: How to write page titles and meta descriptionsWhen pages share a title, search engines cannot tell which one to show, and searchers cannot tell them apart.
What to do: Rewrite each title so it describes that page specifically.
Google will choose its own snippet for these pages, often a poor one.
What to do: Add a description of 70 to 160 characters to each page.
Measured once from our server, so treat it as a rough signal. Slow pages lose visitors and rank lower.
What to do: Look at caching and hosting for these pages in particular.
Images without alt text are invisible to search engines and to screen-reader users.
What to do: Add a short alt description to each meaningful image. Use an empty alt for purely decorative ones.
How to fix this: Image SEO: alt text, file size and layout shiftWithout a width and height, the page shifts as each image arrives. That is the layout shift Core Web Vitals penalise.
What to do: Add width and height attributes to every image tag.
How to fix this: Image SEO: alt text, file size and layout shiftA single H1 tells search engines what each page is about.
What to do: Give each page exactly one H1 that states its topic.
Without it, copies of the page (with tracking codes, for example) can compete with each other in search.
What to do: Add a canonical link pointing at the page’s preferred address.
Paste inside the <head> of the page.
<link rel="canonical" href="https://www.duckdns.org/">
Structured data lets Google show extras such as ratings, prices, opening hours and FAQs in your result.
What to do: Add schema.org markup that fits the business (Organization, LocalBusiness, Product, FAQ).
Paste inside the <head> of the page. Fill in the name and logo address.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "duckdns.org",
"url": "https://www.duckdns.org",
"logo": "https://www.duckdns.org/your-logo.png"
}
</script>These headers protect visitors from downgrade and content-sniffing attacks. Browsers and security scanners look for them.
What to do: Have the web server send Strict-Transport-Security and X-Content-Type-Options: nosniff on every response.
For an Apache server, add to the .htaccess file. On other servers, ask your host to send these two headers.
Header always set Strict-Transport-Security "max-age=31536000" Header always set X-Content-Type-Options "nosniff"
Only 1 H2 subheading found.
What to do: Break the page into sections with H2 subheadings that use the words people search for.
How to fix this: How to write page titles and meta descriptionsThe page does not say which language it is written in.
What to do: Add a lang attribute to the html tag, for example lang="en".
Change the opening <html> tag of every page. Use your own language code if it is not English.
<html lang="en">
This small file tells search engines what they may crawl.
What to do: Add a robots.txt at the root of the site that allows crawling and names your sitemap.
Save as a file named robots.txt at the top level of the site, so it opens at https://www.duckdns.org/robots.txt.
User-agent: * Allow: / Sitemap: https://www.duckdns.org/sitemap.xml
Links shared on X will show as plain text.
What to do: Add a twitter:card meta tag (summary_large_image works for most pages).
Paste inside the <head> of the page. Replace the image address with a picture of 1200 by 630 pixels.
<meta property="og:type" content="website"> <meta property="og:title" content="Duck DNS"> <meta property="og:description" content="Duck DNS free dynamic DNS hosted on Amazon VPC"> <meta property="og:url" content="https://www.duckdns.org/"> <meta property="og:image" content="https://www.duckdns.org/your-preview-image.png"> <meta name="twitter:card" content="summary_large_image">
Assistants quote pages that state a question and answer it plainly. This page has no question-style headings.
What to do: Add a short section of real customer questions as headings, each answered in two or three sentences.
How to fix this: AI search readiness: how to be found by AI assistantsAn optional plain-text summary of the site for AI assistants. It is cheap to add, but there is no evidence yet that it changes how often a site is cited.
What to do: Optionally add /llms.txt with a short description of the site and links to its most important pages.
Optional. Save as llms.txt at the top level of the site. Edit the first lines to describe what you do.
# Duck DNS > Duck DNS free dynamic DNS hosted on Amazon VPC ## Pages - [Duck DNS](https://www.duckdns.org/) - [Duck DNS - spec](https://www.duckdns.org/spec.jsp) - [Duck DNS - about](https://www.duckdns.org/about.jsp) - [Duck DNS - why](https://www.duckdns.org/why.jsp) - [Duck DNS - install](https://www.duckdns.org/install.jsp) - [Duck DNS - faqs](https://www.duckdns.org/faqs.jsp) - [Sign in - Google Accounts](https://www.duckdns.org/login?generateRequest=google) - [Duck DNS - reddit](https://www.duckdns.org/reddit.jsp) - [Sign in to GitHub · GitHub](https://www.duckdns.org/login?generateRequest=github) - [X / Authorize an application](https://www.duckdns.org/login?generateRequest=twitter) - [Duck DNS](https://www.duckdns.org/login?generateRequest=persona) - [Duck DNS - faster UDP under load](https://www.duckdns.org/udp.jsp)
“Duck DNS”
Visitors and search engines get a secure connection.
Nothing on the page blocks it from being indexed.
The page declares a mobile viewport.
Search engines have a list of your pages.
Both forms end at www.duckdns.org.
A made-up address correctly returns a 404, so search engines can drop dead pages.
Images, scripts and styles all load over https.
That is quick.
A reasonable size for the page itself, before images.
Scripts are loaded without delaying what visitors see.
The server shrinks the page before sending it.
Your icon appears in browser tabs and search results.
Nothing in robots.txt shuts out the crawlers behind ChatGPT, Claude, Perplexity or Gemini.
Every internal link we followed loads.
Checked 11 other pages.
| Page | Response | Time | Words |
|---|---|---|---|
Duck DNS https://www.duckdns.org/ | 200 | 0.10s | 34 |
Duck DNS - spec https://www.duckdns.org/spec.jsp | 200 | 0.02s | 644 |
Duck DNS - about https://www.duckdns.org/about.jsp | 200 | 0.04s | 154 |
Duck DNS - why https://www.duckdns.org/why.jsp | 200 | 0.04s | 280 |
Duck DNS - install https://www.duckdns.org/install.jsp | 200 | 1.54s | 5,625 |
Duck DNS - faqs https://www.duckdns.org/faqs.jsp | 200 | 1.42s | 659 |
Sign in - Google Accounts https://www.duckdns.org/login?generateRequest=google | 200 | 0.19s | 32 |
Duck DNS - reddit https://www.duckdns.org/reddit.jsp | 200 | 2.94s | 465 |
Sign in to GitHub · GitHub https://www.duckdns.org/login?generateRequest=github | 200 | 0.09s | 106 |
X / Authorize an application https://www.duckdns.org/login?generateRequest=twitter | 200 | 0.23s | 162 |
Duck DNS https://www.duckdns.org/login?generateRequest=persona | 200 | 0.03s | 96 |
Duck DNS - faster UDP under load https://www.duckdns.org/udp.jsp | 200 | 1.43s | 356 |
Step 2 · Ads
Ads only pay off when the site can measure what they bring in. We look for tracking tags in the page code; tags that load later, through a consent banner or tag manager, will not show up here.
Google Ads cannot learn which clicks turn into customers without it.
What to do: Create a conversion action in Google Ads and add the tag, or import conversions from Analytics.
How to fix this: What to set up before you spend on adsFacebook and Instagram ads need the Pixel to track sales and build audiences.
What to do: Create a Pixel in Meta Events Manager and add it to every page.
How to fix this: What to set up before you spend on adsTikTok ads need the Pixel to measure results and optimize delivery.
What to do: Create a Pixel in TikTok Ads Manager and add it to every page.
How to fix this: What to set up before you spend on adsGoogle Analytics is on the page.
Audit run on . It reads up to 12 pages (60 with a free account) as a search engine first receives them and checks further internal links for errors. Scores are a weighted share of the checks passed.
Run the same audit on your own site, free. No sign-up needed.
This page reports only what our audit observed on public pages of duckdns.org. Adnave is not affiliated with it. If you run this site and something here is wrong, run a fresh audit and tell us.