Why this setup matters for hosted sites

If you want a page to appear in AI Overviews, answer engines, and regular search results, the answer has to show up fast. This tutorial shows you how to build answer-first SEO on AlmaLinux 9, then verify that your pages are crawlable, quick to render, and marked up with schema search systems can read.

The workflow fits Hostperl customers running documentation sites, agency sites, support knowledge bases, and product landing pages on a VPS or dedicated server. If you are still choosing server capacity or want room for staging and log review, a Hostperl VPS is a practical fit for this publishing setup.

This guide uses AlmaLinux 9 because it is a common RHEL-compatible platform for managed sites, reverse proxies, and SELinux-aware hosting stacks. You will create a non-root admin, install Nginx, publish a small answer-first page, add structured data, validate the configuration, and test the result from both server and client sides.

What you will build

You will end with a working Nginx site on AlmaLinux 9 that serves a focused answer page, exposes JSON-LD schema, returns clean HTTP headers, and keeps logs readable for troubleshooting. The page stays simple on purpose. The goal is to make the technical SEO structure visible, not bury it behind a CMS plugin.

• AlmaLinux 9 server preparation
• Non-root sudo user with SSH key access
• Nginx site with answer-first HTML
• Schema markup for a service page or knowledge base page
• Firewall and SELinux-safe configuration
• Verification with curl, grep, and service logs
• Rollback path if you need to revert the test site

Log in and confirm the operating system

On your local computer, open a terminal and connect to the server.

ssh root@203.0.113.10

203.0.113.10 is a documentation example. Replace it with the real public IP assigned to your server.

On the VPS as root, confirm the OS before you make platform-specific changes.

cat /etc/os-release

You should see AlmaLinux 9 in the output. If you are on a different distribution, the package and service commands below will not match exactly.

Create a sudo user and keep root open

Do not close the root session yet. Create a separate admin account so you can test SSH and sudo before tightening access.

On the VPS as root, create the user and add it to the wheel group.

useradd -m -s /bin/bash deploy
passwd deploy
usermod -aG wheel deploy

deploy is the example non-root admin account. Set a strong password when prompted. On AlmaLinux, wheel is the correct sudo group.

On the VPS as root, prepare the SSH directory and install your public key.

mkdir -p /home/deploy/.ssh
chmod 700 /home/deploy/.ssh
cat > /home/deploy/.ssh/authorized_keys <<'EOF'
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEXAMPLEKEYREPLACEWITHYOURREALPUBLICKEY deploy@laptop
EOF
chmod 600 /home/deploy/.ssh/authorized_keys
chown -R deploy:deploy /home/deploy/.ssh

Replace the sample key with your real public key. The permissions matter. SSH will ignore the file if it is too open.

On your local computer, open a second terminal and test the new login.

ssh deploy@203.0.113.10

After you connect, test sudo.

sudo -v
whoami
id

You should see deploy as the user and root only when sudo runs a command. Keep the original root session open until this works.

Update AlmaLinux and install the web stack

On the VPS as the non-root sudo user, update packages and install Nginx plus the tools used in this tutorial.

sudo dnf -y update
sudo dnf -y install nginx curl policycoreutils-python-utils

policycoreutils-python-utils provides the SELinux tools needed to label the web directory correctly. That avoids the common mistake of fixing the firewall and then getting blocked by SELinux.

Check the Nginx version so you know what is running.

nginx -v

Start and enable the service.

sudo systemctl enable --now nginx

Open the firewall and confirm ports

On the VPS as the non-root sudo user, allow HTTP and HTTPS before you place the site online.

sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https
sudo firewall-cmd --reload
sudo firewall-cmd --list-services

You should see http and https in the list. This order matters. Add the new rules before you remove an older access path.

Publish an answer-first page

An answer-first page starts with the direct answer, then supports it with details. For SEO, that means the key fact should appear high in the HTML, followed by a concise explanation and a structured section search engines can interpret cleanly.

On the VPS as the non-root sudo user, create a small site directory.

sudo mkdir -p /var/www/answer-first-seo/html
sudo chown -R nginx:nginx /var/www/answer-first-seo

Create the page content.

sudo tee /var/www/answer-first-seo/html/index.html > /dev/null <<'EOF'


  

    
Answer-First SEO on AlmaLinux 9
    
The direct answer belongs at the top of the page, not buried below the fold.
    
What answer-first SEO does
    
It gives crawlers a short, explicit response, then adds proof, examples, and context.
    
What to watch
    

      
Fast first paragraph
      
Clear headings
      
Valid schema
      
Crawlable HTML
    
  

EOF

This file includes a real title tag, meta description, canonical URL, and JSON-LD. Replace the example canonical URL with your own live URL after the page is published.

Configure Nginx for the site

On the VPS as the non-root sudo user, create a server block.

sudo tee /etc/nginx/conf.d/answer-first-seo.conf > /dev/null <<'EOF'
server {
    listen 80;
    server_name server.example.com example.com;

    root /var/www/answer-first-seo/html;
    index index.html;

    access_log /var/log/nginx/answer-first-seo.access.log;
    error_log /var/log/nginx/answer-first-seo.error.log;

    location / {
        try_files $uri $uri/ =404;
    }
}
EOF

Replace server.example.com and example.com with your real hostname and domain. The separate logs help you isolate this site from everything else on the server.

On the VPS as the non-root sudo user, test the configuration before reload.

sudo nginx -t

If the syntax is valid, Nginx will report success. If it fails, fix the file before you continue.

Reload Nginx after the syntax check passes.

sudo systemctl reload nginx

Fix SELinux labels if the page does not load

On AlmaLinux, SELinux can block access even when the firewall and Nginx configuration are correct. If the page returns 403 or the error log mentions denied access, relabel the content directory.

On the VPS as the non-root sudo user, apply the correct SELinux context.

sudo semanage fcontext -a -t httpd_sys_content_t "/var/www/answer-first-seo/html(/.*)?"
sudo restorecon -Rv /var/www/answer-first-seo/html

If you change the site content path later, repeat those commands for the new path.

Check crawlability and answer structure

At this point, test the page the same way a crawler would. Look for a 200 response, the expected title tag, the meta description, and the JSON-LD block.

On your local computer, request the page from outside the server.

curl -I http://203.0.113.10

You should see HTTP/1.1 200 OK or HTTP/2 200 after you add TLS later. Then fetch the body and inspect the important signals.

curl -s http://203.0.113.10 | grep -E "