WARN: No metatags found


cards dont seem to work but no one responded unfortunately…


Does anyone have any ideas? I’m fairly certain I’ve exhausted the troubleshooting checklist to no avail…


can someone PLEASE help? Is this question really that hard?


What’s the URL? What have you tried?


ive gone through the checklist


Looks like your server is not returning a valid HTTP Content-Type header - see the third bullet point on this page.


I have < meta http-equiv=“Content-Type” content=“text/html; charset=utf-8” /> in my head.

I don’t understand why the bot isn’t detecting this…


It is detecting that, but that is on the last hop after the redirect. Before the redirect, there’s no HTTP header.

curl -A Twitterbot http://vere.cc/topeka -v
*   Trying
* Connected to vere.cc ( port 80 (#0)
> GET /topeka HTTP/1.1
> Host: vere.cc
> User-Agent: Twitterbot
> Accept: */*
< HTTP/1.1 200 OK
< Date: Wed, 24 Oct 2018 21:06:50 GMT
< Server: Apache
< Last-Modified: Sun, 14 Oct 2018 01:26:47 GMT
< Accept-Ranges: bytes
< Content-Length: 961

By comparison…

> GET / HTTP/2
> Host: andypiper.co.uk
> User-Agent: Twitterbot
> Accept: */*
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200
< server: nginx
< date: Wed, 24 Oct 2018 22:05:17 GMT
< content-type: text/html; charset=UTF-8        <------ THIS IS MISSING
< strict-transport-security: max-age=86400


So should I delay the time before redirecting to give the bot more time to detect the tag? Is that possibly the issue?


i see


I’m not talking about the content of the web page, the web server itself is not serving content that our crawler can understand (per the log examples I shared)

The crawler cannot execute Javascript so that solution will not help.

Your Apache web server needs to provide a valid content type header at the protocol level.

closed #13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.