KG-NET combines Training and Education within a clearly agreed scope.
Practical training for your team: WordPress, SEO, e-commerce, Google Ads and automation. We agree the content, format and schedule around your everyday tasks.
KG-NET ACADEMY
Four starting points. Practical lessons.
Read the introductory lessons and try the steps on your own website. Guided team training is planned around your goals and examples.
Understand and review SEO
From a search question to a useful page: three practical checks for your website.
Identify search intent
Write down a real customer question. Is the person seeking an explanation, a comparison or a provider? Open the relevant page and check whether its first answer addresses that need. A service page should explain audience, scope, requirements and the next step. Avoid repeating a page across cities when only the place name changes. Exercise: write three questions a customer needs answered before making an enquiry.
Align title, H1 and body copy
Write a precise page title. The H1 states the main subject; the opening paragraph explains it naturally. Subheadings organize real follow-up questions. Describe informative images with relevant alternative text and use an empty alt attribute for decoration. Check that link text identifies the destination. A fixed number of headings or words is no substitute for a useful explanation.
Measure the effect
Record the URL, date and baseline before changing a page. Use Search Console to review indexing, queries, impressions and clicks. Compare similar periods and account for seasonality and demand. An enquiry becomes a business result only after qualification and follow-up. Also record which contacts match the agreed project objective.
Plan Google Ads with purpose
A clear approach to budget, landing pages and conversion measurement.
Define the goal and budget
Choose the action that matters: a qualified enquiry, a call or a purchase. Agree a reviewable budget and separate advertising spend from management costs. Limit the initial campaign to suitable services and regions so feedback is interpretable instead of mixing every offer into one dataset.
Review the landing page
The ad and landing page must describe the same offer. Check heading, pricing context, scope, contact and mobile usability. Test the form yourself, including a clear confirmation. Avoid invented badges and reviews. A relevant page helps the visitor make the next decision without unnecessary steps.
Verify conversions
Check that a conversion fires once and only after successful completion. Clicking Submit is not the same as a delivered enquiry. Respect consent and regional privacy requirements. Reconcile measured events with contacts actually received. Record tracking changes so reports from different periods remain comparable.
Maintain WordPress confidently
Edit content, separate responsibilities and review changes.
Assign suitable roles
Not everyone needs administrator access. Decide who writes, approves content and manages extensions. Use individual accounts rather than one shared password. Document account recovery and review permissions when staff or suppliers leave the project.
Test changes before release
Back up database and files before an update. Test major changes on a copy, especially forms, navigation, payments and languages. A backup is not enough by itself: verify restoration too. After release, clear the relevant cache and review the affected pages.
Maintain images and copy
Upload images sized for their display and describe their content. Headings define the document outline, not simply a desired font size. Review desktop and phone layouts after saving. Check links, alternative text and a clear next step for visitors.
Integrations and automation
Understand data flows, handle failures and limit access.
Map the process
Describe the source, destination and owner of each data flow. Which fields are required, optional or prohibited? Identify the existing manual step. This makes it possible to assess whether automation is useful and which approvals remain necessary.
Plan for failures
A system must handle invalid data, timeouts and repeated requests. Define safe retries and prevent duplicate records. Logs should support troubleshooting without unnecessarily retaining sensitive content. Decide who receives an alert and how the process can continue manually.
Accept with test data
Use approved test data for initial checks. Verify permissions across roles and revoke access that is no longer needed. Document success and failure cases. Handover should cover start, stop, monitoring and recovery so your team understands how the workflow operates.
