WARN: No metatags found

west_b121 · 2018-10-14T01:20:30.775Z

cards dont seem to work but no one responded unfortunately…

west_b121 · 2018-10-14T23:02:29.163Z

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

west_b121 · 2018-10-16T04:28:52.895Z

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

andypiper · 2018-10-24T18:24:05.924Z

What’s the URL? What have you tried?

west_b121 · 2018-10-24T19:32:25.018Z

ive gone through the checklist

andypiper · 2018-10-24T21:08:11.848Z

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

west_b121 · 2018-10-24T22:02:28.107Z

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…

andypiper · 2018-10-24T22:06:24.837Z

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 198.187.29.27...
* TCP_NODELAY set
* Connected to vere.cc (198.187.29.27) 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
...

west_b121 · 2018-10-24T22:13:42.963Z

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

west_b121 · 2018-10-25T00:03:24.209Z

i see

andypiper · 2018-10-25T01:04:15.076Z

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.

system · 2018-11-15T01:29:31.586Z

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