Updating company data means following a binding process for every change: A responsible person reports the change, the relevant subject matter expert reviews and approves it, the central database is updated, dependent channels are informed, and the result is checked and documented. Opening hours, contact persons, prices, locations, and services should not be corrected separately on the website, in the Google business profile, and on social media profiles.
In my work with small and medium-sized enterprises, I rarely encounter purely technical problems. Most often, the issue is a lack of clear data ownership, documented approval processes, or reliable handover between management, administration, and the people responsible for the website and communications. Even good website data maintenance fails if no one knows who is authorized to initiate changes and which channels are affected.
Company data is only updated once the change has been confirmed against the primary source, stored centrally, published in all dependent channels, and finally verified.
Updating company data: the process in five steps
A functioning change process must remain understandable for a small team. Complex software doesn't resolve unclear responsibilities. For most South Tyrolean SMEs, a process with five mandatory steps is sufficient.
1. Report changes with complete details
Data responsibility begins with the person who first becomes aware of a change. This could be management, administration, sales, the person responsible for human resources, or the manager of a site. A casual message like "Please change the opening hours" is not sufficient.
Each report should contain at least the following information:
- Affected value: for example, telephone number, price, service description or opening hours
- Age status: the currently published or internally valid value
- New status: the future binding information
- Validity date: Date and, in the case of critical changes, also time
- Primary source: approved price list, personnel decision, location decision or duty roster
- Releasing Person: Name and function
- Affected channels: initial assessment based on the dependency list
- Control status: open, in progress or reviewed
- Next inspection date: especially important for seasonal or time-limited information
This compact change record reduces queries and misunderstandings. At the same time, the record forms the core of the change log.
2. Check primary source and release status
Before publication, it must be clear which source is authoritative for a given data type. An email, an old PDF file, and a verbal statement can contain different values. The primary source determines which version is valid.
- For Prices The approved price list or the merchandise management system may be decisive.
- For Opening hours The confirmed operational or deployment plan is crucial.
- For Contact Person It requires internally confirmed responsibility and approval for publication.
- For Locations The address and validity date confirmed by management shall apply.
- For Services The approved service portfolio is decisive, not an outdated brochure.
Changes without a confirmed primary source should not be distributed automatically. Automation speeds up the distribution of correct information, but can also spread unverified errors to multiple channels.
3. Update the central database
After approval, the central database will be updated first. The single source of truth for an SME is the authoritative source from which data is provided on the website, in the language versions, and in other publications.
The central database doesn't need to be a complex system. What's crucial are unambiguous fields, controlled write permissions, a version history, and traceable status. A company can start with a simple solution as long as it remains clear which values are valid and who is authorized to change them.
4. Update website and dependent channels
Publication only follows the central update. A multilingual website requires special attention: any technical change must be synchronized across all affected language versions, page titles, metadata, downloads, and machine-readable outputs.
If structured data provides the same company information to search engines and other systems, these outputs must also be adjusted. I explain in more detail what structured data can do and how it should be classified in the glossary.
Centralized maintenance does not automatically mean that every external channel is technically connected. Some systems can receive data via an interface, while others require manual updates. The change process must cover both scenarios.
5. Check and document the result
The responsible person checks not only the entry in the management system, but also the actual visible output. This includes the website on mobile devices, all language versions, the Google business profile, PDF files, and machine-readable content.
For critical changes, the four-eyes principle applies. A second person compares the published value with the approved primary source. The change log then records timestamps, edited channels, reviewer, outcome, and any outstanding deviations.
The dependency list: Which channels need to be checked?
A dependency list links each data type to its possible output locations. This list prevents only the visible contact page from being corrected, while old information remains in the footer, in an Italian language version, or in a quote template.
Changes to opening hours
- Homepage, contact page and location pages
- all language versions of the website
- Google business profile
- Industry directories as well as tourism and community portals
- Social media profiles
- Map and navigation services
- structured data
- automatic email replies and telephone announcements
- AI files and machine-readable interfaces
In case of a new telephone number or a new contact person
- Contact page, team page, footer and legal notice information, insofar as it is affected
- German, Italian and other language versions
- Google business profile and industry directories
- Social media profiles
- Offer templates, email signatures and presentations
- downloadable PDF files
- CRM, contact forms and forwarding rules
- structured data, AI files and connected interfaces
In case of changed prices or services
- Performance pages and product pages
- Price lists, PDF files and offer templates
- all language versions
- Online shop, booking system or inquiry forms
- Industry portals and sales channels
- structured data
- AI files and connected interfaces
In the case of a new, relocated, or closed location
- Contact and location pages
- Footer, directions and maps
- Google business profile for the respective location
- Map and navigation services
- Industry directories
- Social media profiles
- Letter templates, offers and PDF documents
- structured data and machine-readable location information
The dependency list should not only enumerate where data is located. For each channel, it should also specify the responsible access, the responsible person, and the type of update: automated, manual, or by an external operator.
Five before-and-after examples from everyday SME life
Opening hours: Holiday schedule instead of general override
Previously: A specialty store closes on a public holiday but only changes a notice on its homepage. The Google business profile and the Italian language version still display the regular opening hours.
Afterwards: The administration reports the date and the changed times, management confirms the change, and the information is updated in all affected channels before the holiday. Google recommends entering current and accurate regular hours and using special opening hours for holidays, special events, or temporary deviations, as explained in the Google Business Profile Help Center .
Contact person: Departure without outdated information
Previously: An employee leaves the company. The team page is removed, but her name remains in offer templates, PDF files, email forwards, and the Italian contact page.
Afterwards: The HR manager reports the departure date, successor, and affected contact channels. The central database, all language versions, documents, and forwarding information are updated to the agreed-upon effective date and reviewed by a second person.
Prices: Change with a clearly defined effective date
Previously: The sales department was already using a new price list, while the website and downloadable PDF still displayed the old version. Potential customers received different information depending on the contact method.
Afterwards: The released price list becomes the primary source. The change record contains the old and new prices, the effective date, affected services, and channels. The website, documents, and quote templates are updated on the same date.
Locations: New headquarters in all systems
Before: A craft business relocates and corrects the address in its legal notice. The navigation system continues to direct visitors to the old location because the contact page, Google business profile, and industry directory have not been updated.
Afterwards: The confirmed new address is stored centrally. The dependency list generates specific tasks for the website, language versions, map services, profiles, templates, and structured location data. After publication, the route is tested on a mobile phone.
Services: A new offer with clear responsibilities
Before: A company offers a new service and publishes a social media post about it. The service is missing from the website, the contact form doesn't offer a suitable selection, and external AI responses may still only describe the old portfolio.
Afterwards: The service name, description, target group, responsible contact person, and start date are professionally approved. The change appears synchronously on the service pages, in all languages, in the inquiry form, and in the machine-readable content.
Determine care periods according to risk
Maintenance deadlines should be derived from three factors: potential damage from incorrect information, frequency of changes, and external impact. Incorrect holiday opening hours can lead to customers finding the doors closed. An outdated editorial paragraph is usually less critical.
- Immediately or before taking effect: Closures, new locations, changed telephone numbers, security-related information, legally or operationally binding information and opening hours.
- Within a working day: Prices, available services, sales-related contacts, booking methods and essential delivery or service conditions.
- Within one week: Team texts, references, editorial explanations, images and general company descriptions without direct operational impact.
- Quarterly inventory check: Complete review of website, language versions, profiles, PDF files, structured data, offer templates and important external directories.
The maintenance period doesn't begin only when someone finds time for the website. The decisive factor is the effective date. Therefore, planned changes should be recorded, approved, and prepared for publication in advance.
Clearly separate roles, without unnecessary bureaucracy.
Even a company with five people can clearly define responsibilities. One person may take on multiple roles, but the tasks must be clearly defined.
- Data controller: detects or receives the technical change and reports it completely.
- Person responsible for technical matters: checks primary source, content, validity date and economic consequences.
- Releasing Person: confirms that the new value may be published in a legally binding manner.
- Editor-in-chief: It maintains the central database and initiates manual or technical updates.
- Control officer: For critical data, it compares the visible output with the released data.
- Representation: It takes over the task during vacation, illness, or staff changes.
The issue of representation is often overlooked. A process that only works as long as a single person is present is not a reliable process for keeping content up-to-date.
Maintaining multilingual websites in South Tyrol synchronously
A multilingual website does not consist of independent text versions. If a factual detail changes, that same detail must be updated in every affected language with the same effective date.
The synchronization test includes at least:
- Visible page text in German, Italian and, where applicable, other languages offered.
- Page titles and descriptions for search engines
- Contact and location information
- Form fields and automatic confirmations
- PDF files and downloadable price lists
- structured data and other machine-readable output
- Internal links to changed services or locations
A translation must not replace professional approval. First, the new information is confirmed, then the language versions are transferred and checked. For numbers, dates, names, and addresses, a direct comparison with the approved data set is also advisable.
Why structured data needs its own control
A website can display a new value to users while simultaneously still showing an old value in the background. This can happen when visible content and structured data originate from different fields.
Therefore, after changes to opening hours, location, telephone number, prices, or services, it should be checked whether visible and machine-readable information matches. Technical and content validation of the structured data helps to identify contradictory or technically incorrect values.
The test should answer three questions:
- Is the technical format valid?
- Does the output value correspond to the released primary source?
- Does the machine-readable information match the visible content?
Systematically monitor AI responses
A change to the central database does not immediately correct every response from an external AI system. Depending on the system, AI responses may also take into account information from older or external sources. Therefore, repeatable control questions are an essential part of the change process.
Check for important changes, for example:
- What opening hours does the system indicate for the location in question?
- Who is the contact person for a specific service?
- Which locations and services does the system assign to the company?
- Is an outdated source being used as evidence?
- Do the answers differ depending on the language?
Document the test question, date, system used, answer, and detected deviation. For ongoing review, structured monitoring of AI visibility can be useful. The basis for any correction remains a clear, current, and citable primary source.
Common data maintenance errors
- Change only the visible website: Profiles, PDF files, metadata and structured data remain unchanged.
- Language versions forgotten: The German version is up-to-date, while the Italian and other language versions contradict this.
- Leave old contact persons in documents: Price lists, presentations and offer templates are overlooked during the audit.
- Special opening hours too late to care for: The change will only take effect on the public holiday or after visitors have already found themselves standing in front of locked doors.
- Distribute unverified information automatically: A value that is not released will be transmitted to multiple channels.
- Do not set an expiry date: New prices or opening hours are published too early or too late.
- Do not appoint a representative: Changes will be left untouched during vacation or illness.
- Check only the entry in the system: Errors in the actual website output are not detected.
Questions and answers about the topicality process
Who is responsible for keeping the company data up to date?
The subject matter expert is responsible for accuracy, while the editor in charge implements the approved changes. Management must clearly define roles, deputies, and approval rights to ensure clear allocation of responsibility.
How quickly must changed data be published?
Critical changes must be published immediately or before their effective date. Sales-relevant data should be updated within one business day, less critical editorial information within one week.
How do I manage company data across multiple locations?
Each location needs a unique data record with address, contact information, opening hours, services offered, contact person, and validity status. Changes are approved on a location-specific basis to prevent new opening hours in Merano from being accidentally published for Bolzano as well.
How do I deal with seasonal opening hours?
Seasonal opening hours are recorded with start and end dates before they begin and prepared for the website, language versions, profiles, and structured data. Additionally, the data set requires a follow-up check date to ensure that the correct regular operating schedule is restored after the season ends.
What is particularly important when a price changes?
A price change requires an approved primary source, a clearly defined effective date, and a list of all affected services, documents, and distribution channels. Before publication, it should also be clarified how existing quotes and current agreements will be handled.
What checks need to be carried out when an employee leaves the company?
Check the team page, contact pages, language versions, PDFs, quote templates, email signatures, forwarding rules, forms, and external profiles. At the same time, determine which new contact person will handle inquiries and the effective date of the change.
How do I check whether AI responses use the new information?
Ask documented control questions in the relevant languages and compare the answers with your central database. If outdated information appears, first check the website, machine-readable content, company profiles, and external sources. Immediate updates from every external AI system cannot be guaranteed.
Does a small business need a change log?
Yes, but the change log can be concise. Old value, new value, effective date, source, approval, channels, controller, and timestamp are usually sufficient to make handovers traceable and avoid recurring errors.
Implementation checklist for your company
- Identify a primary source for opening hours, contact person, prices, locations and services.
- Define data controllers, approvers, editors and representatives.
- Define a standardized change record with mandatory fields.
- Create a dependency list for each data type, including all internal and external channels.
- Assign a risk-based maintenance period to each data type.
- Update the central database first, and then all dependent outputs.
- Check each affected language version as well as visible and machine-readable content.
- Apply the four-eyes principle to critical information.
- Document publication, review, and open deviations in the change log.
- Conduct a full inventory check quarterly.
When responsibilities, data structure, and technical updates are disparate, consulting on process design and digitization can help to clearly define roles, data sources, and control steps. The goal is reduced administrative effort: A clear process minimizes conflicting information and provides people, search engines, and AI systems with the same reliable data.
