engagementphoto.pro
AI Engagement Photo Ideas, Poses & Prompt Planner
2 failed · 5 warnings · 22 passed
Audited Thu, 16 Jul 2026 11:00:17 GMT · https://engagementphoto.pro/
Meta & Head
22.2/25
Title, description, canonical, social tags — what search engines read first.
Canonical URLmedium impactlow effort
Canonical href is "/" (not an absolute URL)
Crawlers resolve relative canonical URLs against whatever URL they happened to fetch, so a relative href can silently point your ranking signals at a parameterized or duplicate address. Replace it with the full absolute URL including scheme and host, e.g. <link rel="canonical" href="https://www.example.com/pricing/">. Generate it server-side from a configured base URL rather than from the incoming request's Host header, so staging domains and proxies can't leak into it.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:image tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
7 passing checks
- Title tag<title> is "AI Engagement Photo Ideas, Poses & Prompt Planner" (49 characters)
- Meta descriptionMeta description is "Plan AI engagement photo ideas by scene, city, season, style, outfit, and budget. Explore poses, outfit tips, gallery examples, and copy a moodboard prompt." (156 characters)
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary"
- Page allows indexingrobots: index, follow, max-image-preview:large
Content & Structure
21.9/25
Headings, copy depth, images, structured data, internal linking.
Internal linkingmedium impactmedium effort
0 internal, 0 external links
Search engines discover and rank your pages by following internal links; a page with none is a dead end for crawlers and visitors alike. Add contextual links to related pages on your own site — navigation, related-content sections, and in-body links all count. Aim for at least a handful of relevant internal links per page.
7 passing checks
- Single H1 heading1 h1 found: "AI engagement photo ideas for every scene"
- Heading hierarchy26 headings in order without skipped levels
- Word count4782 words of visible text
- Image alt text2 of 2 images have alt text
- Structured data (JSON-LD)JSON-LD types found: WebSite, WebPage, WebApplication, BreadcrumbList, FAQPage
- HTML lang attribute<html lang="en">
- JavaScript-dependent contentvisible text ~10966 chars in the initial HTML
Technical
21/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Reasonable HTML sizelow impactmedium effort
2.9 MB
A very large HTML document slows parsing on every visit and risks exceeding the portion of a file crawlers are willing to fetch — content past the cutoff may simply never be indexed. Slim it down: move large inline <script> and <style> blocks into external cacheable files, strip embedded JSON data blobs and base64-encoded images, and paginate or lazy-load very long listings. Check the most common culprit first: a framework serializing the entire page state or dataset into the document itself.
HTTP redirects to HTTPSmedium impactlow effort
http:// version serves content without redirecting
Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.
XML sitemap availablemedium impactlow effort
sitemap.xml is valid but robots.txt does not reference it
Your sitemap is valid, but robots.txt never mentions it, so crawlers you haven't manually notified may never find it — the robots.txt reference is the universal discovery mechanism. Add one line to robots.txt: "Sitemap: https://www.example.com/sitemap.xml", using the full absolute URL (a relative path is invalid here). The line can go anywhere in the file, and you can list several sitemaps. Also submit it in Google Search Console to get indexing-coverage reporting on top of discovery.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
8 passing checks
- Served over HTTPSfinal URL uses https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- Fast time to first byte223 ms
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.