Wordpress-Admin Checklist: Creating and checking pages

1. Basic settings:
Short URL
URL format
Vendor or landingpage
Folder
Parent page
Author
Featured image
Meta title
Meta description
Excerpt
Technologies
Vendor heading & subheading
Vendor logo

2. User guidance:
Benefit & user need
Goal & call to action
Text within images
Page scanability
Above the fold
Describe downloads
Describe people

3. Layout & Design:
Centred menu links
Menu item order
Coral lines on headings
Styleguide colours

4. Text:
Automatic spelling & grammar check
Read & carefully correct
Double spaces
Incorrect line breaks
Periods in lists
Phone number format & link
Capitalised button & link texts

5. Images:
Subject
Styleguide dimensions
Use only required sizes
Test for desktop & mobile
High resolution
ALT text, title, file name
File format
110 dpi resolution
60–80% compression
Large images < 200kb

6. Search engine optimisation (SEO):
SEO yes or no
Use keywords
Custom-written texts & images
AI-generated texts
Maximise view time
Page delivers what’s searched for
Page linking
Meta title & description CTR
Content stability & updates

7. AI optimisation:
Structured, explanatory texts
Factual & informative
FAQs & question + answer texts
Explain topics completely
Describe links
Use H1–H5 structure
Textual redundancy
Present information as text
Text formats for AI
AI-generated texts

8. Forms:
Evalanche or WordPress
Description text
Fully visible
Confirmation message
Confirmation e-mail to sender
Confirmation e-mail to admin
Privacy checkbox
Test the form
Test data export

9. Tracking:
Define KPIs / required data
Set up tracking
When and what data to whom
Test data format

10. Potential problems:
Redirects for URL changes
Links to deactivated pages
External links in new tab
Internal links in same tab
Contact, e-mail & phone number Links
Space between “Vendor Team”
Remove empty blocks
New menu for new pages
Test menu links
No spaces in links

11. Custom Solutions:
Link to email with subject text
Link to a block on a page
Open pages in iFrame
Expandable FAQ/info block
Different images/blocks for desktop & mobile
Open content by clicking on link
Change text color via HTML
Transfer page URL to Evalanche

1. Basic settings

1. Is the page URL short (called “title form” and “slug” in WordPress), does it include important keywords, and avoids spaces, umlauts, and stop words? (Wrong: /become-a-msp-and-use-the-infinigate-msp-contract-templates | Correct: /msp-contract-templates)
2. The correct URL format is e.g. https://www.infinigate.com/en/vendor/extreme-networks/
   (Lowercase only (!), with https (not http), with www, and trailing slash if no parameters follow)
3. Vendor page or landing page? Product/service = Vendor page | Campaign/other = Landing page
4. Select folder for the page (e.g. Landing Pages > Vendors > Microsoft).
5. Select parent page (e.g. Landing Pages > Vendors > Microsoft). The parent page becomes part of the URL (e.g. https://www.infinigate.com/en/lp/v/microsoft/my-landing-page/)
6. Select yourself as author of a new page if you are the main owner/editor especially for cloned and imported pages where somebody else might be selected.
7. Select featured image (OG image), use styleguide image dimensions (1200×630). Edit page > top right. This image appears as the preview when shared on social media.
8. Enter meta title (“SEO title”) (approx. 30 to max. 60 characters, use important keywords)
   (e.g. Become a Microsoft Reseller Partner). The meta title appears in the browser tab and in Google search results.
9. Enter meta description (approx. 70 to max. 150 characters, use important keywords) (e.g. Become a Microsoft Reseller Partner with Infinigate – Request a demo and pricing today.) It shows as the short description in Google search results.
10. For vendor pages, events & news, enter the excerpt (in WordPress this is called “excerpt”) (Edit page > top right, 1–2 sentences).
11. For vendor pages, events & news, enter technologies (Cybersecurity, Secure cloud, Secure networks).
12. For vendor pages, enter heading and subheading (1–2 short sentences).
13. For vendor pages, add vendor logo (“Vendor logo”), which appears at the top right of the page. (Edit page > scroll down > Vendor logo). Select from existing logos under Media > Vendors, logo upload and preparation done beforehand by Vanessa.
    If you ever upload a new vendor logo yourself, always rename it before uploading into WordPress into e.g. microsoft-logo.svg with an additional word beside the vendor name like “-logo”.

2. User guidance

1. Does the page have a clear benefit and address a need of the visitor?
2. Does the page have a measurable goal that is supported by calls to action?
3. Do not use Texts within images, expecially if it holds vital information.
   If there is text within images, that needs to stay, it must be fully visible and legible on both desktop and mobile.
4. If I only look at the headings, images, and buttons on the page, is the structure and navigation clear? (Users typically scan the page quickly top to bottom before reading body text.)
5. If I only see the above-the-fold area without scrolling, is it immediately clear what the page is about, what to expect, and what value continued reading provides?
6. If download buttons are used, is it briefly and clearly stated in or above the button what exactly is being downloaded?
7. If photos of known people are used (e.g. instructors, testimonials, employees), it should always be clear who they are (name, role, relevance to the page topic).

3. Layout & design

1. If a menu is used, are the links in the blue menu centred at the top? (Vendor pages and others with a top menu.)
2. If a menu is used, are the standard entries in the same order as on other vendor pages? Solutions | Become a partner | Demo equipment | Project registration | Contact
3. Are the coral lines next to headings used consistently? Lines only for main headings (H2), not for subheadings or sublines.
4. Are the styleguide colours used correctly? Styleguide

4. Text

1. Copy the page completely and paste it into Word. Run automatic spelling and grammar check.
2. Zoom in and manually READ the entire text THOROUGHLY for errors (content, grammar, spelling) (IMPORTANT!!!)
3. Use the search function to find double spaces. (Shortcut: CTRL + F, enter two spaces)
4. Remove incorrect line breaks. (Line breaks in the middle of sentences may look fine on desktop but cause formatting issues on narrow mobile screens)
5. Are final periods in lists used consistently?
   (Rule: Full sentences = period, single words or no sentence = no period)
6. A correct phone number link format is e.g. for Germany with country code 0049: tel:+498989048123 (no spaces, no hyphen)
7. Button texts and standalone link texts begin with a capital letter: Learn more, Read more, Download now.

5. Images

1. Please create images from our Canva-templates.
2. Please use the styleguide for image usage and dimension-table above if you have to create images without Canva templates.
3. Does the image subject fit the page topic, evoke the intended emotions, or help convey the content?
4. When using additional images, the image file dimensions should match the maximum display size (To check: open the page in browser at 1920×1080, right-click the image > Inspect)
5. Is the image usable and clear on both desktop and mobile?
6. Is the image sharp and high-resolution?
7. Add ALT text, title text, and file name for every image, using important keywords.
   (e.g. ALT & title = Managed Services contract templates, filename = managed-services-contract-templates.jpg)
8. JPG should be used for most images such as photo style imagery.
   PNG is only for logos (or SVG), for graphs, infographics and all images that have flat colours and solid shapes.
   PNG may provide better quality but also needs much more filesize that slows down the website.
   SVG for logos or icons has high quality and a very small filesize.
9. The image resolution should be 110 dpi if you create images outside of Canva.
10. The image quality / compression rate should be 60 to 80 (60% = more compression, less quality, smaller filesize) and must not cause visible quality loss. Please test which compression/quality is required based on the image content.
11. The file size of large images should not exceed 200kb.

6. Search engine optimisation (SEO)

1. Does the page need to be optimised for Google, or is it not necessary? Not all pages should appear in Google for specific keywords (e.g. password-protected pages, post-form pages, terms and conditions, directions, surveys, etc. will not or don’t need to appear in Google)
2. To help users find the page, important keywords should appear in the URL, title, headings, body text, image filenames, and descriptions. To select the best keywords for your page, get in touch with Jan Amelsberg.
3. Text and images should be original and created specifically for this page, not copied from other sources. Google values unique content more than copied or stock material.
4. AI-generated texts or passages may be considered less valuable by Google in the future compared to human-written content. Test them using:
   ZeroGPT SEO.ai Sapling and rewrite if score is above 10%.
5. User dwell time on the page should be maximised. (Engaging content, page interaction, videos, podcasts, etc.)
6. The user ideally finds the answer to their question or what they’re looking for and doesn’t return to Google to continue searching on other websites.
7. The page should receive internal links from as many topic-related subpages as possible, and potentially external backlinks through promotion and organic-looking link-building from related sites.
8. Include outgoing links to high-quality, topic-relevant external websites and internal subpages.
9. Especially important pages should be linked from the navigation and homepage.
10. The meta title and meta description shown in Google results should work together as an attractive ad that encourages clicks.
11. Updates: The page should be regularly updated with new text and images to signal freshness to Google. (As often as possible, several times per year; the responsible person is the CMM.)
12. Stability: The content should remain mostly intact during updates and only be supplemented. Replacing all or large portions of content harms SEO rankings.

7. AI optimisation

1. Structured, explanatory texts are better understood by AIs than fragmented information.
2. A factual, informative writing style is more valuable for AIs than casual language or hype-heavy buzzwords.
3. Explain topics in full on a single page without needing to link to external information.
4. Clearly describe links to help AI understand the linked content or page purpose.
5. Use a heading structure from H1 (highest) to H5 (lowest) to logically organize the page.
6. Textual redundancy, when used sparingly, can reinforce key information in varied wording to highlight importance to AI.
7. Write information as text, not embedded within images, animations, videos, or menus.
8. FAQs & question + answer formats provide compact, structured information ideal for AI processing & SEO like via the Yoast FAQ WordPress-block.
9. Use optimal text formats for AI such as glossaries, comparisons, process descriptions, checklists, and use cases.
10. AI-generated texts or passages may be rated less valuable by AIs in the future than human-written content. Test these using:
    ZeroGPT SEO.ai Sapling and rewrite when scores exceed 10%.

8. Forms

1. Should the form data be automatically sent to the CRM? Use an Evalanche form embedded via iFrame (WordPress block “Custom HTML”).
2. If the form data should not be sent to the CRM, but instead e-mailed to recipients and exported in WordPress as CSV, use a WordPress form.
3. Is there a clear and concise headline explaining what the form is for and why it should be filled out? (e.g. “Download free whitepaper now”)
4. Is the entire (Evalanche) form and the submit button visible?
5. Should an optional confirmation e-mail be sent to the user?
6. Include a privacy checkbox at the end.
7. Test the form thoroughly: Fill it out and send. Is the data transferred correctly to CRM / WordPress / e-mail?
8. Is the confirmation message correct and does it include any further calls to action?
9. Check the notification e-mails (to Infinigate and possibly also the user).
10. Plan the data export (what, when, to whom).

9. Tracking

1. What data will be used to evaluate the goals of the page? (Visitor numbers, form usage, form data, etc.)
2. Is the tracking for this data already set up? (Lead form, Matomo, external tools like GoToWebinar, etc.)
3. When and how will the data be delivered to the employee who uses it? (Real-time, daily, monthly, via e-mail, in WordPress, etc.)
4. Is the data format usable for the employee? (CSV, Excel, PDF, etc – send an example and ask to be sure)

10. Sources of error

1. Changing the “title form” (slug) changes the page URL. For already published URLs, a redirect to the new URL may be necessary, and all links in the content of other subpages must be updated.
2. If the URL of the page is deactivated, all links in the content of other subpages pointing to this URL must be removed.
3. Are all links to external domains set to open in a new tab?
4. Are all internal links set to open in the same tab?
5. Is the correct mailto: link behind all visible e-mail addresses?
6. Is the correct mailto: link behind the “Contact us” button in the contact block?
7. Is the correct tel: link behind all visible phone numbers?
8. “Vendor Team” with space (wrong: MicrosoftTeam / Microsoft-Team, correct: Microsoft Team).
9. Have all empty WordPress blocks been removed?
10. If a page with a menu was cloned, a NEW menu must be created and swapped for the new page. Otherwise, changes affect BOTH pages!
11. Test each menu link and, if needed, also on subpages to ensure you can return to the main page.
12. Links should have no spaces at the beginning or end (wrong: My link correct: My link)

11. Custom Solutions

1. Link to e-mail address with predefined subject text:
   Send email
   Set link to: mailto:beispiel@infinigate.com?subject=Dein%20Betreff
   Space: %20
   „: %22
   :: %3A
   Ä: %C4
   Ö: %D6
   Ü: %DC
   ä: %E4
   ö: %F6
   ü: %FC
   ß: %DF
2. To open a URL in a page in an iFrame, e.g. for an Evalanche form, add an HTML block in WordPress and copy this code for a height of 800px and change the URL:
   <iframe scr=“https://www.domain.com“ height=“800″></iframe>
3. Expandable FAQ/Info block such as on „Social Engineering“ the block „Frequently Asked Questions“:
   A script is needed here. Please send the texts to Jan Amelsberg.
4. Different blocks and images for desktop & mobile:
   The „Visibility“ setting of a WordPress block determines via „Browser & Device“ for which device it should or should not be displayed. So you create 2 similar blocks and only display one at a time.
5. Open content by clicking on the link:
   The „Visibility“ setting of a WordPress block determines via „Query String“ on which URL it should or should not be displayed. For example, enter the following in the String field: dl=enabled
   And only show a download block if ?dl=enabled is at the end of the URL.
   I can set a link to this URL and show the block by clicking on it.
6. To change the text color via HTML, use this code and change the color value:
   <p style=color: #0073e6;“>Dies ist blauer Text.</p>
7. To transfer the URL of the page to Evalanche, e.g. to track marketing activities on different pages that can use the same form, a custom script must be built into the page and a field must be added in Evalanche. Please contact Jan Amelsberg for the setup.

11. Custom Lösungen

1. Link auf E-Mail Adresse mit vorgegebenem Betreff-Text:
   E-Mail senden
   Link setzen auf: mailto:beispiel@infinigate.com?subject=Dein%20Betreff
   Freizeichen: %20
   „: %22
   :: %3A
   Ä: %C4
   Ö: %D6
   Ü: %DC
   ä: %E4
   ö: %F6
   ü: %FC
   ß: %DF
2. Um eine URL in einer Seite in einem iFrame zu öffnen, z.B. für ein Evalanche Formular, einen HTML-Block in WordPress hinzufügen und diesen Code für eine Höhe von 800px hineinkopieren, sowie die URL ändern:
   <iframe scr=“https://www.domain.com“ height=“800″></iframe>
3. Aufklappbarer FAQ/Info Block wie beispielsweise auf „Social Engineering“ der Block „Häufige Fragen“:
   Hier wird ein Script benötigt. Bitte die Texte an Jan Amelsberg senden.
4. Unterschiedliche Blöcke und Bilder für Desktop & Mobile:
   Durch die Einstellung „Sichtbarkeit“ eines WordPress-Blocks wird über „Browser & Device“ festgelegt, für welches Gerät er angezeigt bzw. nicht angezeigt werden soll. Man erstellt also 2 ähnliche Blöcke und zeigt jeweils nur einen an.
5. Inhalte durch Klick auf Link öffnen:
   Durch die Einstellung „Sichtbarkeit“ eines WordPress-Blocks wird über „Query String“ festgelegt, auf welcher URL er angezeigt bzw. nicht angezeigt werden soll. Im Feld String z.B. folgendes eintragen: dl=enabled
   Und einen Download Block nur einblenden, wenn am Ende der URL ?dl=enabled hängt.
   Auf diese URL kann ich einen Link setzen und dadurch den Block per Klick einblenden.
6. Um die Textfarbe via HTML zu ändern, diesen Code nutzen und den Farbwert ändern:
   <p style=color: #0073e6;“>Dies ist blauer Text.</p>
7. Um die URL der Seite zu Evalanche zu übertragen, um z.B. Marketingaktivitäten auf unterschiedlichen Seiten zu tracken, die dasselbe Formular nutzen können, muss ein custom-script in die Seite eingebaut werden und ein Feld in Evalanche hinzugefügt werden. Bitte für das Setup an Jan Amelsberg wenden.

Questions and suggestions:

E-mail to Jan.Amelsberg@Infinigate.com