The shape of it. SiteGround uses its own panel, Site Tools, rather than cPanel. And it asks one job of you that no other host does: taming its cache. Skip that one, and the install will feel haunted.
The ordinary start. Run the preflight check, then in Site Tools open File Manager, go into public_html, upload the PageMotor zip and extract it there. You should end up with pagemotor.php, a lib folder, and config-sample.php. If you got a single folder called pagemotor instead, move everything inside it up one level.
On a Mac? Safari often unpacks a downloaded zip by itself. Upload the .zip exactly as downloaded, and never zip the unpacked folder again: a Mac-made zip adds a hidden __MACOSX folder, and the files then land one level too deep. If Downloads shows only a folder, download the zip again.
The SiteGround part. Every site runs a full-page cache called Dynamic Cache. It is on by default, there is no off switch in Site Tools, and its only built-in manners are for WordPress and Drupal. Everything else, PageMotor included, gets cached like an ordinary page for up to twelve hours. That includes the install screen, the admin area, and the login.
The kill switch. In public_html, edit or create .htaccess, and set Cache-Control to private at the very top. Then flush the cache in Site Tools, under Speed, Caching, Dynamic Cache. The flush is not optional: SiteGround only applies .htaccess caching changes after one. To check it worked, load any page and look at the x-proxy-cache header. BYPASS or MISS is what you want. HIT means the cache is still answering.
The database. SiteGround chooses the names for you: create the database and it generates one, create the user and that is generated too, with the password shown exactly once in a notice, so copy it now. And here is the step nearly everyone misses: a freshly created user has access to nothing. Go to Manage Access, pick your database, and give it all privileges, or PageMotor is turned away at the door.
The rename. config-sample.php becomes exactly config.php, and that rename is what switches PageMotor on. Put the three generated values into DB_NAME, DB_USER and DB_PASSWORD. DB_HOST stays localhost.
Finishing. Flush the cache, visit your site, then go to /admin/ and create your admin user. And straight after creating it: flush the cache again, clear your browser's cookies for the site, and only then log in. That one-two is what prevents the login loop.
“The user login cookie was not created!” Your browser really did get the cookie. The problem is the next page, which the cache answers with a copy saved before you logged in, so PageMotor never runs and never sees it. Break the loop in order: log out or close the tab, flush Dynamic Cache, delete the site's cookies, then log in again. On SiteGround, when in doubt, it is the cache.
SiteGround only. If you try to connect Claude to the site, SiteGround's Anti-Bot AI blocks the sign-in handshake, and you cannot fix it yourself. It parks a challenge under /.well-known/, which is exactly where PageMotor publishes the documents Claude has to read. Three things make it hard to spot. It answers 202, a success code, so error-hunting checks call the site healthy. It is keyed to the requesting IP, so your own browser sees the correct JSON while Claude is challenged. And it leaves /mcp/ alone, which sends people hunting inside PageMotor for a fault that is not there. Only a SiteGround support ticket lifts it.