Yes, there is a limit of 100 "records" within each folder. A record includes items such as contact records, a map location and an image/logo. You can also have up to a maximum of 3,000 folders within your .tel.
How to improve your directory structure
A .tel resource can be as simple and nimble as a personal business card, or as complex and multi-faced as an online directory service. However, many large organizations and directories have difficulties fitting everything into one .tel, and instead integrate multiple .tel domains into a framework.
Feedback from directory builders shows that shorter lists and navigational paths score highest with visitors, so More isn't always Better. Ultimately, users want to find the phone number they're looking for in only a few clicks. The simplicity and speed become especially important when browsing on a mobile device due to screen limitations and costly traffic.
When developing your .tel, think about the optimal navigation paths and the presentation of information on each page. Speed and accessibility are key differentiators when promoting a .tel resource, so keep thinking about usability and the mobile market while building your .tel structure. And whatever you do, don't leave empty folders – there's little worse than hitting a dead end after 5 or 6 navigational layers.
Ultimately, as a .tel builder, you need a "secret formula" that will take into account the overall amount of information you wish to publish, the target audience of your project, their goals and browsing habits, the devices (mobile or PC) that they will use, and the amount of time and effort they will be prepared to spend on your .tel resource. You will also need to cater for the potential growth of your project and the hosting limitations in place.
To avoid excessive navigation, multiple .tel domains can be used to make up a project. This can be illustrated with mind maps. In our examples below, arrows outline the navigation flow, and numbers 1 to 3 show levels.
Example 1: Talfen.tel links to individual resources like LebanonCinemas.tel. The overarching project Talfen can still get the most marketing, and can serve as a hub for the mass of new entries, while niche .tel domains host specific information and can be used independently for subsequent queries.
Example 2: MaVille.tel by Richard Desjardins (see interview at page 5). In this setup, "My City" project relies on several town .tel domains, each working as an independent directory.
Example 3: Praha.tel contains some information under its own navigational tree, but also relies on other .tel services, such asPocasi.tel ("weather") – which is shared among a number of local city directories, such as Brno.tel and Luberec.tel. Unlike the previous examples, this model has more than one master project—one for each city and service.
Summing it up, city directories often use multiple .tel domains to organize their data by category or geographical area, and generate additional cross-links for search engine optimization. Thus, a joint .tel model improves the experience for customers, and brings more traffic and usage through search engines.
So what's next – a pan-American directory of accountants? A worldwide network of carpet manufacturers? A galaxy reunion for saving the green Earth?