Skip to main content
OpenAIAnthropicGooglePerplexityMetaMicrosoftAmazonCohere
WordPress Operations

read every log your WordPress site writes. from the dashboard.

access logs, error logs, the PHP error log, the FPM slow log, and a record of which crawlers and AI bots hit each page — all per site, live, with no SSH session to open.

free trial. no credit card required.

includedYovale WordPress Hosting - Log Viewer
yovale.com/en/features/logs
built into the hosting layer

the logs Yovale surfaces per site.

When a WordPress site throws a 500 or a plugin starts misbehaving, the answer is almost always in a log — but most hosts hide logs behind SSH, vague paths, or a support ticket.

01
access
every HTTP request to the site
02
error
server and nginx errors
03
php-error
fatal errors and warnings from PHP
04
fpm-slow
requests that ran past the slow threshold
01
Access and error logs
02
PHP error and FPM slow log
03
Crawler and AI-bot log
04
Live tail in the dashboard
operational map
1Open the site's logs

Pick a WordPress site in Yovale and open its log view — no SSH key or path needed.

2Choose a stream

Switch between access, error, PHP, FPM slow, and crawler logs for that specific site.

3Tail and search

Watch the log live or search it to find the request, error, or bot you're after.

status panel
live
tail logs from the dashboard
per-site
scoped to your container
0
SSH sessions to read a log
live
tail logs from the dashboard
per-site
scoped to your container
0
SSH sessions to read a log
operational view

every log, scoped to your site, in real time.

log access is part of the dashboard, not a server skill you have to keep.

Access and error logs

see every request and every server error for the site, as it happens.

primary capability
PHP error and FPM slow log

find the plugin or theme behind a fatal error or a slow request.

supporting control
Crawler and AI-bot log

see which search and AI crawlers hit which pages, and when.

supporting control
Live tail, no SSH

stream logs in the dashboard instead of hunting for paths over SSH.

primary capability
the problem

on most hosts, reading a log means an SSH key and a guess about paths.

When a WordPress site throws a 500 or a plugin starts misbehaving, the answer is almost always in a log — but most hosts hide logs behind SSH, vague paths, or a support ticket.

By the time you've found the right file, the spike has passed. logs should be in the dashboard, scoped to the site, and readable in real time.

Where logs live
×SSH, vague paths
in the dashboard, per site
Reading live
×tail over SSH if you can
live tail in the browser
PHP and FPM logs
×find the path yourself
one click per stream
Crawler visibility
×parse raw access logs
search and AI-bot log built in
Papertrail
Loggly
Typical hosts
debugging

go from 500 error to root cause faster.

When something breaks, the error and PHP logs are right there next to the site, already filtered to it.

You read the actual error instead of reproducing it blind.

visibility

see who and what is hitting your pages.

The crawler log shows search and AI bots — Googlebot, GPTBot, ClaudeBot, and others — against the pages they request.

You can tell real indexing from noise without parsing raw access logs by hand.

built-in, not bolted on

SSH-and-guess vs Yovale log viewer.

$0 - included on every plan

access
php error
crawler
live
tail logs from the dashboard
access
Open the site's logs

Pick a WordPress site in Yovale and open its log view — no SSH key or path needed. every HTTP request to the site server and nginx errors

per-site
scoped to your container
php error
Choose a stream

Switch between access, error, PHP, FPM slow, and crawler logs for that specific site. fatal errors and warnings from PHP requests that ran past the slow threshold

0
SSH sessions to read a log
crawler
Tail and search

Watch the log live or search it to find the request, error, or bot you're after. search and AI-bot hits per page live stream, searchable, no SSH

Crawler and AI-bot log
How to read WordPress logs on Yovale
pricing and comparison

log tools charge per gigabyte. Yovale includes log access.

access, error, PHP, FPM, and crawler logs are part of every plan.

yovale pricing
$0/included

included on Starter ($149/yr), Growth ($249/yr), and Business ($499/yr).

Standard Host

Where logs live
SSH, vague paths
Reading live
tail over SSH if you can
PHP and FPM logs
find the path yourself
Crawler visibility
parse raw access logs
Access needed
SSH key and server know-how
Costexternal tool or no access

Yovale Log Viewer

Where logs live
in the dashboard, per site
Reading live
live tail in the browser
PHP and FPM logs
one click per stream
Crawler visibility
search and AI-bot log built in
Access needed
your dashboard login
Cost$0 - included on every plan
faq

common questions before you switch.

Which logs can I see?

Access, server error, PHP error, the PHP-FPM slow log, and a crawler log showing which search and AI bots hit each page — all per site.

Do I need SSH to read logs?

No. Logs are in the Yovale dashboard, scoped to each site, with a live tail and search. There is no SSH key or path to find.

Can I see which crawlers and AI bots visit my site?

Yes. The crawler log records search and AI bots such as Googlebot, GPTBot, and ClaudeBot against the pages they request.

Are the logs scoped to my site?

Yes. Because each site runs in its own container, the logs are that site's logs — not a shared server's mixed output.

Is log access included on all plans?

Yes. Log access is part of every Yovale plan.

ready when you are

stop SSHing in to read a log. see them all in Yovale, free.

live tail. per site. no server skills required.